83% of developers suffer from burnout. So let's talk: what does burnout look like? And how can we prevent it?

In this 142nd edition of Console by CodeSee, we are interviewing Simon of Tube Archivist! We also feature projects that covers UI and CMS.

Refactoring is easy—as long as you don’t work with other people or touch anybody else’s code.

In this 141th edition of Console by CodeSee, we are interviewing Orhun of git-cliff! We also feature projects that covers frameworks and emulators.

In this 140th edition of Console by CodeSee, we are interviewing Udayraj of OMR Checker! We also feature projects that covers GPT to terminals and app notifications.

How many developers at Southwest warned managers and the executive team that they needed to upgrade their legacy system? All of them.

In 2022 we featured over 160 open source projects in the Console by CodeSee newsletter! Can you guess which language dominates the top 10 projects (as determined by attention and engagement): Clojure, Go, Ruby, Rust, TypeScript, or Vue?

Do non-coders on your team, like sales and marketing reps, management execs, understand how your app works? See how with code visibility tools like CodeSee developers can communicate effectively about technical decisions to all members of your product development team.

For developers taking on a new team member, often the most difficult part of onboarding is not so much the code but the business logic.

Onboarding is not a one-size-fits-all process; having a variety of approaches will help people with differing personalities and skillsets adapt effectively to your team.

We can't always be as productive as we'd like; behavioral and environmental factors may be contributing to a slower development cycle. Learn how to overcome six barriers to fast-paced software development.

CodeSee's latest release is live on Product Hunt. Take a minute or two and share your thoughts on the #1 Code Visibility Platform to help us get Product of the Day.

In this post, we’ll cover what code visibility is, compare what development looks like with and without code visibility, and consider how CodeSee enables code visibility.

CodeSee is no longer just a map of your files--it's a full code visibility platform. Discover new features like Code Automation, premium security features, and pull requests (PRs) across repo services (CodeSee Service Maps).

Developers today shouldn't blindly traverse directories, reviewing the general structure of code. Learn why code visibility-GPS for your codebase is invaluable for your organization and how CodeSee delivers the code visibility you need.

In December 2021, our team was asked to share our reasons for supporting the Open Source Initiative, and our hopes for the open source movement.

Refactoring is the act of restructuring code without impacting the current functionality. Refactoring does not fix bugs or add new features, but it does improve the design of the code and the health of the codebase. Good developers know this and refactor their code frequently. But what if you’re

Check out this 2-minute video for guidance to help you get more out of your Maps experience using Tours and Tour Alerts.

Today marks a milestone at CodeSee. In this post, we share exciting company news and insight into what’s on the horizon.

At CodeSee, we’re very confident that we’re onto something big with our mission to fix the code visibility problem plaguing development organizations. But it sure does feel great to receive major validation of our vision in the form of a prestigious industry award. We announced today that CodeSee

Communicating about code is hard. The way we write code is not the way we talk about code. Since we hold most our code in our heads, sometimes jotting down our thoughts is surprising helpful. Yet, most note taking tools allow you to capture your thoughts but don’t allow

I was devastated. Two days before the launch of Docker Security Scans, we found a bug. The new feature, which would show security vulnerabilities on Docker images, wasn’t showing the same number to users that we had on the backend. It quickly became clear that there was no simple

When I first taught myself to code, I noticed a gap. Even though I’d been teaching myself to code for five years, I didn’t have the skills necessary to reach the next level. I was technical… but not technical enough. It wasn’t just me who noticed this