Kevlin Henney and Daniel Terhorst-North take on one of the most enduring, and controversial, ideas in software engineering: clean code.

Since the publication of Robert C. Martin’s (Uncle Bob) Clean Code, generations of software developers and software engineers have been taught that “cleanliness” in code is the gold standard. But what does clean code really mean in modern software development? And does it still hold up in today’s complex, fast-moving systems?

Kevlin and Daniel explore how the idea of clean code evolved — from Bob Martin, Kent Beck, and even earlier thinkers in computer science — and challenge whether rigid rules and dogma actually help developers write better code, or whether they sometimes make systems harder to understand and change.

This conversation goes beyond style guides and naming conventions to focus on what truly matters:

How code supports human understanding
- Why habitability may be more useful than “cleanliness”
- How context, scale, and team dynamics change what good code looks like
- When refactoring and design practices actually improve outcomes — and when they don’t

-

Kevlin on X ➡️ https://x.com/KevlinHenney
Kevlin on LinkedIn ➡️ https://www.linkedin.com/in/kevlin/
Kevlin on bluesky ➡️ https://bsky.app/profile/kevlin.bsky.social

Daniel on LinkedIn ➡️ https://www.linkedin.com/in/tastapod/
Daniel On Mastadon ➡️ https://mas.to/@tastapod 
Daniel on bluesky ➡️ https://bsky.app/profile/did:plc:ejuui7c3riyggntey6yt5nm5

Modern Software Engineering on X ➡️ https://x.com/ModernSoftwareX
Modern Software Engineering on LinkedIn ➡️ https://www.linkedin.com/company/modern-software-engineering
Modern Software Engineering on bluesky ➡️ https://bsky.app/profile/modernswe.bsky.social

-

⭐ PATREON:

Join the Continuous Delivery community and access extra perks & content! ➡️ https://bit.ly/ContinuousDeliveryPatreon 

🎥 Join Us On TikTok ➡️ https://www.tiktok.com/@modern.s.engineering

-

👕 T-SHIRTS:

A fan of the T-shirts I wear in my videos? Grab your own, at reduced prices EXCLUSIVE TO CONTINUOUS DELIVERY FOLLOWERS! Get money off the already reasonably priced t-shirts!

🔗 Check out their collection HERE: ➡️ https://bit.ly/3Uby9iA
🚨 DON'T FORGET TO USE THIS DISCOUNT CODE: ContinuousDelivery

-

#softwareengineering #cleancode #developer #software #programming

Continuous Delivery

Kevin Henney and Daniel Terhorst-North explore whether "clean code" is a timeless principle or dogmatic myth. They trace the term's origins from 1970s programming texts through Robert C. Martin's influential 2008 book, examining how context shapes code quality. The discussion emphasizes that cleanliness isn't about rigid rules like function length, but about habitability—code that developers can navigate comfortably and change confidently. They argue clean code should be judged relationally: does it serve the team's current constraints and goals? Historical practices like extreme decomposition made sense when teams were siloed, but modern full-stack development benefits from locality of behavior—keeping related code together. The key insight: clean code is a means to sustainable software delivery, not an end in itself.

"Clean Code" a Timeless Truth OR a Myth We Keep Telling Ourselves?

<p>clean code is based on solid principles and design pattern, so yes. is the most important principle.</p>


<p>Kevlin Henney. With an L.
<a href="https://kevlin.tel/" target="_blank" rel="noopener nofollow">https://kevlin.tel/</a></p>
