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.

In this episode we re-visit the talks about company culture, this time with guest speaker Thomas Morris.

In this episode Jeffrey talks about an old manager who never seemed to be content with his deliverables, even if he met the acceptance criteria exactly. Isaac adds more to the conversation around managers that are too strict versus managers that are too aloof.

In this episode Jeffrey and Isaac discuss the common phases of a rewrite cycle, and how iteration eliminates complexity.

In Episode 9 we start our first of many 'F*ck-up Fridays', where we talk about an interesting or crazy thing that has happened to a company we've worked at. Today Isaac talks about an early startup he worked for that ultimately failed after its customers were raided by the FBI.

Brian Begy is a guest in this week's episode. Brian shares his experience with companies that have attempted to transform software built for internal processes to using and selling it as a service.

Jeffrey brings up the concept of risk in this episode, tying it back to our previous conversation with guests Nathan Keyes and Colleen Grafton in Episode 4 where we discussed their project 'Nozomi'.

In this episode Isaac and Jeffrey discuss patterns they've seen in both highly performant and poorly-performing teams - how team culture is shaped, how overall company culture helps shape it, and why trust is one of the most important drivers of great teams.

Jeffrey introduces the concept of 'perverse incentives' for rewriting - reasons for rewriting that are pushed not for a better product or for the customer, but for the benefit of the engineers or the manager responsible for the project.