Never Rewrite: Software Engineering & AI Coding

In this episode, Day Martin, founder of Swayday, shares her journey from creating a standing desk company to developing motion gaming experiences aimed at improving educational outcomes for children with ADHD. The conversation explores the iterative process of game development and the importance of feedback. Day notably reuses instead of rewrites the gaming code of her pilot gaming project to pivot towards an idea with better traction.

Show Notes

Swayday: https://swayday.com/Times Tables: AR Space Game: https://apps.apple.com/az/app/times-tables-ar-space-game/id6743813232

Isaac and Jeffrey discuss the challenges faced in recovering value from failed projects, particularly focusing on a specific project that was halted due to legal concerns. They explore the importance of A-B testing, the role of legal feedback, and the lessons learned from the experience. The discussion emphasizes the need for quick iterations, optimizing processes for future projects, and maintaining a positive team attitude in the face of setbacks.

Isaac Askew and Jeffrey Sherman discuss the significance of making incremental changes visible in software development. They emphasize the importance of metrics in measuring performance, system reliability, and user behavior. The discussion covers A-B testing, decision-making based on data, and real-world applications of metrics in projects, highlighting how these practices can lead to better outcomes and improved communication within teams.

Isaac Askew and Jeffrey Sherman discuss the ongoing debate between end-to-end tests and unit tests in software development. The discussion delves into the implications of the testing pyramid, the potential future of testing with AI, and the evolving role of product teams in the testing process. They emphasize the need for a balanced approach to testing, cautioning against over-reliance on end-to-end tests while recognizing their value in certain scenarios.

In this episode of Never Rewrite, hosts Isaac Askew and Jeffrey Sherman engage with Spriha Tucker, the Field CTO at BuildKite, to explore the intricacies of Continuous Integration and Continuous Deployment (CI/CD). They discuss the importance of deployment in CI/CD practices, the significance of feedback loops in iterative development, and the necessity of understanding customer context for effective solutions. Spriha shares insights on the role of a Field CTO, the value of communication in development teams, and strategies for rapid prototyping. The conversation emphasizes building trust with customers and the importance of de-risking in the development process, ultimately highlighting that CI/CD is about more than just tools—it's about creating value for customers through effective collaboration and feedback.

Isaac and Jeffrey discuss why abandoned projects or failed rewrites have code that always seems to just linger - is it worth fixing?

In this episode of Never Rewrite, Isaac Askew and Jeffrey Sherman emphasize the importance of understanding customer needs and the risks associated with maintaining old features while developing new ones. The conversation highlights the value of iterative delivery and the significance of API versioning in ensuring a smooth transition for users. Ultimately, they advocate for a pivoting approach rather than a complete rewrite, allowing for a more adaptive and responsive development process.

(Isaac used the wrong microphone for recording and Jeffrey said nothing...)

Today we highlight he significant impact and costs associated with hidden business rules in software development. We explore the challenges of implementation, the importance of documenting business rules effectively, and how AI can assist in managing these rules. Our discussion emphasizes the need for an internal product book to consolidate knowledge and improve communication among teams, ultimately leading to more efficient development processes.

Isaac Askew and Jeffrey Sherman discuss the social and emotional ramifications of failed rewrites in project management. They explore the loss of patience from leadership, the burnout experienced by teams, and the importance of taking responsibility for project outcomes. The discussion emphasizes the need for teams to salvage lessons from failures and to approach leadership with solutions rather than just problems. The conversation concludes with strategies for ensuring future success and maintaining trust within teams.

Chapters

00:00 The Impact of Failed Rewrites

03:03 Team Dynamics and Leadership Pressure

06:01 Salvaging Lessons from Failure

09:00 Taking Responsibility for Project Outcomes

12:02 Strategies for Future Success

Isaac Askew, Dustin Rea, and Jeffrey Sherman delve into the complexities of developing Minimum Viable Products (MVPs) and the challenges of balancing simplicity with the need for future scalability. They discuss the Goldilocks problem in software development, emphasizing the importance of finding the right balance between over-engineering and under-engineering. The discussion highlights the distinction between maintainability and optionality, the significance of timing in product development, and the lessons learned from past experiences. The trio also explores the concept of gaming out scenarios to prepare for potential challenges and the importance of aligning teams to ensure a cohesive approach to development.