

#1622
Mentioned in 15 episodes
Clean Code
A Handbook of Agile Software Craftsmanship
Book • 2008
In 'Clean Code: A Handbook of Agile Software Craftsmanship,' Robert C. Martin provides practical advice, best practices, and principles to help software developers write high-quality code.
The book emphasizes the importance of code readability, changeability, extensibility, and maintainability.
It covers various aspects such as naming conventions, function design, comments, and testing, with a focus on making code easy to understand and modify.
Martin also introduces several key concepts, including the 'Boy Scout Rule' and the 'Law of Demeter,' to improve coding practices.
The book emphasizes the importance of code readability, changeability, extensibility, and maintainability.
It covers various aspects such as naming conventions, function design, comments, and testing, with a focus on making code easy to understand and modify.
Martin also introduces several key concepts, including the 'Boy Scout Rule' and the 'Law of Demeter,' to improve coding practices.
Mentioned by



















Mentioned in 15 episodes
Mentioned by 

as a resource for understanding clean code principles in JavaScript.


Scott Tolinski

36 snips
The Fundamentals — JS
Mentioned by 

as a highly regarded and also hated piece of work.


Carson Gross

21 snips
The CEO of htmx likes codin' dirty (Interview)
Erwähnt von ![undefined]()

als ein Buch darüber, wie man Code schreiben soll.

Garrelt Mock

16 snips
Deep Dive 183 – Vite mit Dominik Göpel
Mentioned by ![undefined]()

in relation to a clean code video series used for team training.

Philip Markgraf

16 snips
Living Documentation with Philip Markgraf
Mentioned by ![undefined]()

, who contributed to the second chapter of it.

Tim Ottinger

11 snips
Agile Otter on why most devs work in the worst ways possible
Mentioned by 

as one of the books read and discussed on the podcast.


Carter Morgan

John Ousterhout and Robert "Uncle Bob" Martin Discuss Their Software Philosophies
Mentioned by ![undefined]()

when questioning if classic software engineering practices are still relevant in the age of AI.

Joe Reis

Freestyle Fridays - High on Crazy Pills
Mentioned by 

as having a dominant idea in coding that he doesn't agree with entirely.


Carson Gross

The CEO of htmx likes codin' dirty (Changelog Interviews #646)


Robert C. Martin

Uncle Bob Martin: Software Leader - Episode 357
Mentioned by ![undefined]()

as a book he was asked to review.

Charles Maxwood

Pioneers of Computing: A Journey Through Tech History with Bob Martin - JsJ 671
Holger kann Clean Code nicht empfehlen.

Folge 113: Patterns Schmatterns - Gang of four in 2025
Mentioned by 

as a book that "A Philosophy of Software Design" subtly rebuffs.


Carter Morgan

"A Philosophy of Software Design" by John Ousterhout
Mentioned by 

as a series of books written by 

to share his software career wisdom.


Adam Stacoviak


Robert C. Martin

Back to Agile's basics (Interview)
Referenced by 

as a popular but divisive book on how software should be written.


Carson Gross

The CEO of htmx likes codin' dirty
Mentioned by 

when discussing the technical aspects of clean code.


Robert C. Martin

Clean Code for Managers: Robert C. Martin, a.k.a. Uncle Bob
His arguments are mentioned in relation to code optionality and upfront investment.

Not For Us! - 99 Bottles of OOP by Sandi Metz, Katrina Owen, & TJ Stankus
Mentioned by 

in the context of a debate with John Ousterhout on software design philosophies, leading to an updated version of "Clean Code."


Nathan Toups

Balancing Features and Systems Improvements - The Good News Factory by Kent Beck
Mentioned by Brian as a more famous version of 'Clean Code in Javascript'.

#259 - The Minimum Effective Dose of JavaScript You Need to Learn
Mentioned by ![undefined]()

when discussing the importance of practice and iteration in programming.

Ryan Fleury

Debuggers and programming from scratch with Ryan Fleury!
Mencionado por ![undefined]()

ao discutir como aplicar todas as ideias de um mega framework pode ser um problema.

Sibelius Seraphini

#238 - Más práticas em desenvolvimento de software com Sibelius Seraphini