Never Rewrite

This episode explores an iterative refactoring workshop run by Jeffrey to improve development skills. It discusses code selection, refactoring techniques, working independently, and the benefits of the workshop.

In this episode Isaac defines impostor syndrome and ways to combat the feelings that you aren't qualified for your 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).

Using the concept of a straw man, the hosts discuss how it can facilitate conversations and help overcome creative paralysis. They also explore the fear of correction versus creation and share tricks to encourage conversation and creativity, emphasizing the importance of effective communication.

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.

The hosts discuss the concept of MVPs and the challenges of deciding what features should be included. Exploring the concept of Minimum Viable Product (MVP) and its importance in different scenarios. Using a pre-existing product integration as an MVP and leveraging it to build one's own product. Delving into the ongoing discussions surrounding the definition of Minimum Viable Product (MVP). The importance of capturing interest in an idea and having a strong user base.

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.