Isaac and Jeffrey discuss the challenges and signs of failing rewrites in software development.

Nick Stinemates from System Initiative joins us to explore the complexities and challenges of software rewrites. We discuss the nuances between rewrites and refactors, the pitfalls of full rewrites, and the importance of incremental changes. The conversation delves into team dynamics during rewrites, the existential reasons that can drive a rewrite, and the parallels between software rewrites and software adoption.

Show Notes:

Nick's X account: https://x.com/nickstinemates

Jeffrey and Isaac explore the complex trade-off between providing immediate relief for software issues versus investing time and resources into finding a permanent cure. They discuss the implications of these choices on customer satisfaction, business budgets, and the overall health of software systems. Through real-world examples, they illustrate how sometimes quick fixes can be more practical than ideal solutions, emphasizing the importance of understanding the context and priorities of a business.

Isaac, Dustin, and Jeffrey discuss the challenges faced by non-technical founders when working with developers. They explore issues of trust, communication, and the importance of iterative development. The discussion emphasizes the need for clear frameworks in product development, the significance of addressing technical debt and security concerns, and how to identify red flags in developer behavior. The conversation concludes with advice on balancing survival and enhancement in development and the importance of having technical expertise in-house.

Guest Dan Hon discusses the complexities and risks associated with rewriting government software, particularly in the context of social security systems. He emphasizes the importance of understanding legacy systems, the role of ideology in software development, and the need for transparency and user-centered design. The discussion also touches on lessons learned from the private sector and the challenges of modernization in government services.

Show Notes:

Dan's LinkedIn: https://www.linkedin.com/in/danhon/

Dan's Newsletter: newsletter.danhon.com/

Reference to Jamie Zawinski: https://www.jwz.org/gruntle/nomo.html

Original Wired.com article: https://www.wired.com/story/doge-rebuild-social-security-administration-cobol-benefits/

Isaac Askew and Jeffrey Sherman discuss DOGE's proposed rewrite of the Social Security system, focusing on the implications of transitioning from COBOL to a modern programming language like Java. They explore the motivations behind the rewrite, the challenges of legacy code, the potential role of AI, and the human cost of possible failures. The conversation culminates in predictions about the outcome of the rewrite and the impact on millions of Americans relying on Social Security.

Show Notes:Wired Magazine article referenced: https://www.wired.com/story/doge-rebuild-social-security-administration-cobol-benefits/

Isaac tells a 'fulfilling Friday' story about how he gained the attention of a famous tattoo artist. He just needed to act quickly and send money to secure the appointment...

Isaac Askew and Jeffrey Sherman discuss the complexities of testing infrastructure changes with guest Rob Gonnella. They explore the importance of building a robust testing infrastructure, the role of different types of tests, and the challenges faced when transitioning to new systems. Rob shares his experiences in developing local testing environments, engaging developers, and identifying bugs through end-to-end tests. The conversation emphasizes the need for a balanced approach to testing, particularly when making significant infrastructure changes.

Never Rewrite is going analog! Out of 2000 minutes over the last two years we think we've got plenty of content to coalesce it into a book. If you have a rewrite story to share, now's your chance to get forever immortalized in the podcast hosted by two randos.

Jeffrey and Isaac explore the motivations and expectations surrounding software rewrites from various stakeholders, including developers, IT leadership, product groups, marketing, finance, support, and customers. They discuss the perceived benefits and the reality of rewrites, emphasizing that while many believe rewrites will lead to improved reliability and a better work environment, the truth is that rewrites often fail to deliver on these promises.