Guest Contribution: 3 Tips For How To Be A Good Steward Of A Codebase

Being a good steward of a codebase means more than just writing functional code, it’s about contributing in a way that respects the team and the work that came before you. In this blog, we share three practical tips: assimilate the existing style to keep the codebase consistent and readable; communicate before making changes to avoid unnecessary risk or confusion; and lead with compassion when working with legacy code, recognizing that every line was written under different circumstances.

C3 Meet up: Designing for Testability

At July’s C3: Code, Craft, Community meetup, we focused on designing for testability. Using a real-world scheduling problem, developers practiced Test Driven Development, pure functions, and the Single Responsibility Principle to break down complexity and write cleaner, more testable code.

Pair Programming: How to be a Good Partner

Learn how to become a better programming partner with three practical tips for improving your pair programming experience. From open communication to humility and gratitude, this blog shares key insights to help you collaborate more effectively and write better code together.

Learning in the Community: How C3 Builds Better Developers and Teams

C3: Code, Craft, Community, a monthly meetup we host that brings together developers from all levels and backgrounds to sharpen their skills, pair program, and explore the deeper questions behind great software development. We don’t just talk about learning. We practice it, publicly and together.

Client Factors of Software Projects

This post explores three critical factors that can make or break a project: earning client buy-in, maintaining regular demonstration and feedback loops, and providing proactive support post-launch. Through real project experiences, the author shares lessons learned about aligning with client expectations, course-correcting early, and empowering clients to succeed long after go-live. These insights remind us that delivering real value means listening first, collaborating often, and supporting always.

C3: Code, Craft, Community Meet up

In May, we tackled a flash card kata that explored Test-Driven Development and how to write testable code around unpredictable inputs like time and randomness. Through hands-on coding and open collaboration, we walked away with new tools for abstraction, mocking, and cleaner test coverage.