Community

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

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!

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.

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.

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?

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 December 2021, our team was asked to share our reasons for supporting the Open Source Initiative, and our hopes for the open source movement.

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.

A collection of codebase onboarding stories from real developers.

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

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