Never Rewrite: Software Engineering & AI Coding

Today we discuss the relationship between Conway's Law and software quality, exploring how a company's structure and culture can impact code quality. We delve into the signs of a toxic culture, the consequences of a 'yes culture', and strategies for identifying and changing company culture. The conversation emphasizes the importance of communication patterns and the long-term nature of cultural transformation in organizations.

We debate the merits of consolidating technology stacks versus diversifying them. Today we explore the implications of each approach on business value, engineering efficiency, and organizational dynamics. Key points include the importance of evaluating the business value of consolidation, the impact on developer fungibility, and the balance between engineering optimization and business leverage.

Jeffrey and Isaac dive into a comment made by Allen Holub to 'rebuild' instead of 'rewriting' legacy software and dive into the terminology.

Show Notes:‪

Allen Holub's thread mentioned: https://bsky.app/profile/allenholub.bsky.social/post/3lmcyvi3kag2f

Isaac and Jeffrey explore how to halt a rewrite, the importance of learning from the process, and how to effectively communicate changes in direction to a team. The conversation emphasizes the value of reframing discussions around rewrites to focus on new insights and solutions rather than perceived failures.

Guest Nick Gerace discusses the rewrite of the core engine at System Initiatives, detailing the challenges faced, the technical decisions made, and the importance of aligning development with business goals. The conversation covers the transition from the old engine to the new, the role of user feedback, and the iterative process that led to a more efficient and user-friendly product.

Show Notes:

Domain-Driven Design book: https://www.oreilly.com/library/view/domain-driven-design-tackling/0321125215/

Nick's LinkedIn: https://www.linkedin.com/in/nickgerace/

Guest Paul Stack shares his experiences in transforming a massive logging infrastructure from a monolithic architecture to a microservices-based system. He discusses the challenges faced during the transition, the implementation of Kafka for log management, and the importance of data retention and cost management. The conversation highlights the evolution of logging practices and the empowerment of teams through decentralization, ultimately leading to a more efficient and effective infrastructure.

Show Notes:

Paul's LinkedIn: https://www.linkedin.com/in/stack72/

Paul's Github: https://github.com/stack72

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.