Using CodeSee Maps for Refactoring
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
A CodeSee Guide: Using Labels and Notes
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,
The pragmatist’s guide to low-stress architecture diagrams
There's a hurdle that makes working with software architecture diagrams harder than it first seems. Whether it's a formal system, such as UML, or something you make up on the fly, every software architecture diagram relies on standards. That leaves you with a choice to make.
Why create software architecture diagrams?
There are three core reasons why architecture diagrams 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 large codebase * Outward communication: they&
Code smarter: Become a Senior Software Engineer quickly
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