Cloud Engineering

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.

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.

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.

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.

An agile mindset can be a powerful tool in overcoming imposter syndrome. By embracing flexibility, continuous learning and collaboration, individuals can shift from a fixed mindset to one that values growth and improvement. By focusing on small wins, adapting to change and being open to feedback, those struggling with imposter syndrome can reframe their mindset and recognize their true potential.

As consultants, we’re often asked to improve an existing application for a client. It’s a challenge we’re well versed in but it can be a painful process, especially when the current tech stack wasn’t designed with future growth in mind.