Welcome to CodeSee Learn.

...the IT world has been buzzing about microservices, with many organizations hopping on the bandwagon to reap the benefits. However, some teams are now making a surprising reversal...

Interview with Marcelo of Pretty Maps - Draw pretty maps from OpenStreetMap data

Onboarding to unfamiliar code can be daunting. CodeSee codebase maps and interactive product tours simplify the process and shorten the time-to-effective metric.

In this edition of Console, we're interviewing Louis of Gleam - a language for building type-safe, scalable systems. We also featured two OSS projects such as react.dev and Miller!

Code Automations Quick Start

Got a refactor in your future? Follow our 4 steps to ensure it's a success: Plan, Review, Map, and Automate.

In this 144th edition of Console by CodeSee, we are interviewing Abdelrahman of VeeValidate! We also cover projects that includes avatars, file transfers and tracking!

In this 143rd edition of Console by CodeSee, we are interviewing Mark of GUN! We also cover projects that includes background tasks, budgeting and encrypted applications.

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?

First issue of CodeSee Product News gives insights into how you can clone yourself with Code Automation; showcases the codebase map of Distribute Aid, one of the founding members of our Open Source Community, Code Automation, and more!

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 this guide, we've shared a few of our favorite Maps types, along with tips on getting the most out of your Maps.

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

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).

How humanitarian aid organization, Distribute Aid, makes a massive impact using CodeSee to onboard new contributors.

How humanitarian aid organization, Distribute Aid, makes the most of each minute in code review with CodeSee.

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

Explore the motivations, needs, and experiences of the contributors who engage with your open source project.

Learn how to make the contributor experience of open source projects feel more enjoyable.

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

On January 20, 2022, CodeSee announced it has raised $7 million in additional funding, bringing the company’s raised total to $10 million.

More intuitive code reviews with Review Maps in VS Code.

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,

Join Ramón for a video tour of OSS Port!

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

Company Offers First Ever Platform to Help Development Teams Visually Understand Complex Codebases

A collection of codebase onboarding stories from real developers.

We’re CodeSee, and we’re on a mission to help developers improve how they navigate and understand today’s increasingly complex codebases. Solving an age-old challenge Since the advent of computer programming, not a lot has changed in the approach to onboarding developers to a project. Even today, most

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

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

SAN FRANCISCO (August 10, 2021) – CodeSee, the world’s first solution for continuous understanding of large codebases, has been named one of the 20 Rising Stars as part of the sixth-annual Forbes 2021 Cloud 100 list, the definitive list of the top 100 private cloud companies in the world, published

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

We know how long you spend trying to understand code, whether it’s a new part of the codebase, code you haven’t touched in a while, or just a flow in your app that seems to change with every PR. Our mission at CodeSee is to help you develop

You know when you are reading through code or stepping through a debugger and you see a callback function being passed around and you think: “I really just want to go to where the callback actually gets executed” but you can’t? You just can’t? function myCallback(data) { } function

We’ve adopted an approach to build in the open, and we’ll use this forum to let you know where we’re headed. Developers in our early access program have installed CodeSee to record their app and inspect their source code, runtime data, loops, nested functions, all in code

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

When I joined CodeSee [https://www.codesee.io/] as Head of Design in March, I knew it was to build a suite of insanely useful tools for developers – to explore everything that happens when you run your app, gain insights about how the code works, record your knowledge, and share

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

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