Isaac and Jeffrey continue discussions around testing brownfield code, delving deeper into next steps and refactoring.

Brownfield code is existing code (rather than new code) that you might need to add tests for. Join us for a two-part episode on how to get started testing and refactoring existing applications.

Isaac and Jeffrey discuss ways to improve yourself outside of traditional means like college, courses, or reading.

A non technical story of deception, good deeds with terrible consequences, and weak HR.

Sometimes an upgrade to a new version of a framework takes weeks or even months. What do you do when you need to make changes to areas that are being affected by the upgrade?

Special Guest Aadil Farid joins us again to continue his discussion on the harsh realities he confronted when he led a team that computerized ticketing on India’s Railways in the 1980s.

Special Guest Aadil Farid joins us to discuss the harsh realities he confronted when he led a team that computerized ticketing on India’s Railways in the 1980s.

Special guest Brian Genisio from Khan Academy joins us to talk about their 3.5 year rewrite that successfully wrapped up this year. Learn how Brian’s team was able to achieve the nearly impossible act of successfully completing a rewrite using many of the techniques we’ve talked about in the past, plus some brand new ones! If you want to learn about what it takes to do a rewrite, buckle up!

AI tools can now write your incident retrospectives. Do developers lose by not formalizing their thoughts by writing? In this episode Isaac and Jeffrey weigh the pros and cons of having AI write incident retrospectives and documentation.

Senior DevOps Engineer Rob Gonnella joins us in this special episode to live workshop an example of a rewrite case he believes is valid.

Jeffrey has been running an iterative refactoring workshop to improve his colleague’s development skills. This episode dives into how the workshop is run, what the developers get out of it, and how it directly improve’s the company’s codebase. If you’ve ever wanted to help your fellow developers but didn’t know how to start, this show is for you!

In this episode Isaac defines impostor syndrome and ways to combat the feelings that you aren't qualified for you job.

Sometimes companies shrink instead of grow, and that impacts your work, your team, and your career. In this episode we discuss what to expect from a shrinking company.

Jeffrey identifies a strategy we employed in a previous project that helped us dramatically improve the experience of 90% of our customers without requiring a complete rewrite of an email sending engine.

Isaac discusses strategies he's used to help companies upgrade their software, and Jeffrey helps distill them into a series of steps.

In this episode Jeffrey discusses a f*ck-up of his own for this special 'F*ck-Up Friday' series - how a develop lost $1 billion (just for a little while).

Jeffrey suggests using a straw man to help facilitate difficult conversations about how to proceed; Isaac adds further examples and methods by which teams can generate productive conversations.

In this episode Jeffrey brings up red flag development ideas that should make you second guess whether or not you're making the right decision for your product.

In this episode Isaac and Jeffrey discuss the concept of a product MVP and misconceptions around what a 'minimum viable product' has to be.

Josh Beckman is our guest in this episode where we talk about his experience in successfully transitioning multiple micro services back into a monolith - and why it was the right decision.