
Tidy First?: A Personal Exercise in Empirical Software Design
About this episode
We'll be discussing Kent's approach to writing cleaner, more maintainable code by emphasizing small, incremental improvements he calls "tidyings."
● Learn why Kent believes software design is fundamentally about human relationships, starting with the programmer's relationship with themselves.
● We'll explore the concept of "tidying first" – making small, strategic changes to the structure of your code before diving into feature implementation.
● Discover practical examples of tidyings, like using guard clauses, eliminating dead code, and writing self-documenting code that reduces the need for comments.
● Understand the economic forces at play in software development and how tidying can increase your options and reduce long-term costs.
Whether you're a seasoned developer or just starting out, this episode offers valuable insights into writing code that's a joy to work with. Tune in and discover how "tidying first" can revolutionize your approach to software development.
Get every episode summarized
Each time Tech Book Podcast publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.
Email me new episodesFree for 3 shows. No card needed.
Hosts & guests
No transcript yet
This episode has not been transcribed. Request it and it moves to the front of the queue.
More episodes
More from Tech Book Podcast

Site Reliability Engineering: How Google Runs Production Systems
Tech Book Podcast

Software Engineering at Google
Tech Book Podcast

Clean Architecture by Robert Cecil Martin
Tech Book Podcast

Soft Skills: The software developer's life manual
Tech Book Podcast