Guide

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

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

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.

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.

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.

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

Code review is essential to shipping quality code. Here are two tools to help automate parts of your code review process.

How I use CodeSee to take on large codebases with greater confidence (and better results).

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

Advice on creating a repeatable and reliable code review checklist for your team.

Ensuring a smooth developer onboarding process is essential for companies. In this post, learn how to improve your developer onboarding path using the 10-3-10 test.

Codebases are complex and constantly evolving. Helping you navigate them with greater ease and understanding is our leading goal at CodeSee. One way we make this possible is with Maps Labels and Notes. While the feature may seem simple, its awesomeness is all in the application. With Labels and Notes,

There's a hurdle that makes working with software architecture diagrams [https://www.codesee.io/architecture-diagram] harder than it first seems. Whether it's a formal system, such as UML [https://en.wikipedia.org/wiki/Unified_Modeling_Language], or something you make up on the fly, every software architecture diagram relies on

There are three core reasons why architecture diagrams [https://www.codesee.io/architecture-diagram] make sense for even moderately sized codebases: * Coherent vision: they provide a clear statement of direction and of decisions made * Collaboration: they make it easier to onboard new developers and to work across different parts of a

We've all been there. Coding away, solving a problem when all of a sudden we hit a blocking point. The thing we're trying to do doesn't work, or the problem seems completely out of reach. Heck, sometimes we might not even know how to begin solving the problem! This might

It’s not just you: Writing code is way more fun than reading it! Taking the time to read, process and understand a piece of code let alone a codebase can take heaps of work. That said, as codebases grow in size and complexity, as dependencies increase and adapt over

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