Code Obsession

 Constraints make great engineering. They aren't always a bad thing, and understanding them can help you make better coding decisions. In this episode, Dave and Allan discuss many different common constraints. Some are more obvious like technology, time, and budget. Others are easily missed but still useful: people, org charts, and culture. https://crafting-code-podcast.github.io/episodes/026-constraints.html

 Bits do not rot when left alone, but the world around the code changes. Over time, although the code itself has not changed, the value provided by it will effectively rot away. In this episode, your hosts talk explore this topic; from video games and antiquated coding paradigms to the Red Queen hypothesis and software gardening. https://crafting-code-podcast.github.io/episodes/025-code-rot.html

 TL;DR Lean software development and mobbing as mutually supporting techniques. From the Mob Mentality YouTube page: Chris Lucian and Austin Chadwick discuss all things #agile and product development from a #MobProgramming perspective. Join us in this thoughtful episode of the Mob Mentality Show as we explore the world of Lean Software Development with Dave Adsit. Titled "Crafting Lean Software: Dave Adsit on Small Batches and Short Lead Times," this episode provides valuable insights for those looking to enhance their software development values and practices. Dave Adsit shares his experiences on how to effectively implement lean principles to achieve small batches, short lead times, and frequent releases. Key Discussion Points: #### *Lean Software Development* - *Craft vs. Engineering* - *Principles of Flow* - *Waterfall vs. "Agile" vs. Lean* - *Timeboxes vs. Scope-Boxes* - *Resource vs. Flow Efficiency* - *Prioritization, Prototyping, and Lean Investment Bets* -

TL;DR It's a jam packed episode with Etienne about coding in the 80s, leadership roles, lean software development, experimentation and learning, and effective communication. From the CTO Podcast site In this conversation, Etienne and Dave reminisce about their early experiences with computers and programming. They discuss the different computer models they had, the challenges of typing in code from magazines, and the evolution of technology. They then shift the conversation to their roles as VP of Engineering and CTO, and the differences between the two positions. They talk about the importance of product management and design in software development, and the value of delivering in small batches. They also discuss the concept of lean software development and the economic mindset behind it. The conversation explores the conundrum of developers being resistant to working on new features and instead over-engineering existing ones. The fear of the unknown and the comfort of familiarity

Are we unintentionally doing things which reward bad behavior? Sometimes company policies incentivize people to do the wrong thing, like coming to work sick because they've run out of sick days. Although we rarely have control over company policies, we can look for ways that our teams reward bad behaviors. In this episode, Dave and Allan share some examples of bad behaviors we've seen, in the hope that we can influence our teams, managers, and companies to think about what we incentivize and how we might act differently. https://crafting-code-podcast.github.io/episodes/024-rewarding-bad-behavior.html

Technical debt is a metaphor which is thrown around a lot, but what is is really? In this episode, Dave and Allan discuss the metaphor and how well it holds up when compared to financial debt. Regardless of the name, we have to spend time and money addressing this unavoidable, perennial problem. So what can we do about it? https://crafting-code-podcast.github.io/episodes/023-technical-debt.html