Clean Code, Second Edition.

“claude, read Clean Code, Second Edition and then implement this feature. make no mistakes”

Please please please record an audiobook with you as the narrator, delivered entirely in the same borderline unhinged presentation style you use in these vids. It would be epic.

Look for We, Programmers in audiobook.

Oh excellent. 😁

here i wrote the foreword for you: Foreword: A Prompt Engineer’s Guide to Clean Code Here is the truth about being a developer: your real job is not to “innovate” or “architect elegant systems.” Your real job is to clean up slop. Always has been. Always will be. You spend 90 percent of your time scraping half-baked code off the floor like a short-order cook on the night shift. And now we have AI. Which means the slop is coming faster. It is not just dripping in anymore, it is gushing out of a firehose labeled “Productivity Boost.” One sloppy prompt and the AI cranks out 10,000 lines of pure, unfiltered nonsense before you can blink. We are drowning in AI slop. Slop that hallucinates APIs that do not exist. Slop that uses libraries last updated in 2003. Slop that is written in five languages at once because “polyglot” sounded cool. Slop that compiles but only if you are on Windows XP running on a potato. The machines are not our saviors. They are slop factories. They will happily generate endless piles of code with the confidence of a toddler holding a crayon mural. So what do we do? The same thing we have always done. We clean. We refactor. We rename variables that make us weep. We extract functions until they actually make sense. We turn “AI slop” back into something a human can read without losing faith in humanity. Clean Code is not just a discipline anymore. It is pest control. It is janitorial duty at scale. It is our only defense against exponential slop production. So grab your mop, your linter, and your sense of humor. The slop is not going away. It is multiplying, and it is our job to clean it. Do it with no bugs, make sure it is secure, and keep the vibes happy. And above all, may your token guesser never, ever break production. —Barrett

Even if I tend to disagree with the old Clean Code, I'll still be buying this if not for anything else just because Uncle Bob's attitude and joy for writing and sharing his knowledge and opinion is so damn infectious. Keep up the good work

I'm not Uncle Bob (I'm cousin Robert) but if I was Uncle Bob writing a second edition I would have done the whole thing Clojure

I did virtually all of “Functional Design” in Clojure.

nice!

just wondering what lessons did you learn in the last few years of not writing production grade code? what kind of valuable perspectives will you add? or is it just piggy-backing on the existing "clean code" branding and addressing all critique currently out there?

One has to wonder what would motivated a smart young man to ask such a puerile question.

genuine curiosity first edition is increasingly criticized, no doubt you've picked up on this. second edition seems to acknowledge these criticisms - would love to hear which principles you've reconsidered after watching the industry evolve from the sideline

No JavaScript Bob, no JavaScript...

I’ve bought multiple copies of clean code and gave them as gifts to colleagues. It has had a profound impact on my career. I’ll definitely purchase the second edition when it becomes available.

Is it possible to have clean code in JavaScript? Asking for a friend.

Of course.

😇

Thanks, Bob! That’s great to hear.

Can we now write longer functions? 🥲

I keep mine pretty short, but you do you.

Does this make the first edition obsolete? I got the first and I still haven't gotten around to reading it.

So this would be the clean code, clean book edition? 😁 Awesome, it's going on my Christmas list!

I guess my question to you - knowing nothing about code as a simple end user - is that usually you are so very sure about your convictions in your current posts - it's admirable. But then...how did you change after 16 years? So in 16 years from now you'll change your convictions?

Readers will not see a change in my convictions. What they will see is a much broader nuance and dialogue.

Why no JavaScript 😢

There is JavaScript too.

I will be buying this book.

I was doing a boot camp for OOP and Clean Code was the the “Text Book” we used. Valuable knowledge :)

Read the first edition to clean code. Read the second edition to clean, clean code.

Would love to hear your thoughts with TypeScript! It seems to have a good few caveats compared to Java/C#/Python/Go etc. that can make Clean Code difficult, especially for frontend use

Never really caught my interest. I’ve avoided static typing over the last decade and a half.

I found Clean Code about 12 years ago just as I was wondering how to organize my code. It is a gem.

Can’t wait to read it!

Still can't clean code, how do I get the water outside the closing brackets in a C code

When? I need to know when!!

Now.

Plans have just changed.

Just curious but Are you authorizing this book for use in coding agents like Claude and ChatGPT?

Are three lines functions still a thing?

People keep asking me questions like that. It must be that they listened to someone else critiquing someone else’s critique of someone else’s critique of Clean Code.

I actually read it entirely, kept the best and discarded the rest.

Would be great if you collaborated with regional publishers to make a copy available in India as well.

Thanks Bob!

🐐 is back!

Uncle Bob, I ran a book club on "Clean Code" a couple of jobs ago, & it was awesome. Now, years later and further in my career, I am pushing for our book club at my current job to do "Clean Code" 2nd edition. You did the coder world a great favor, man, and you've done it again.

Waiting for a delivery… Amazon says it might take a couple of weeks 🫠🇩🇪

Oh God yes… 👍 Thanks for the great books at least two generations of developers have read or should have read 😉

Me lo voy a pedir para los Reyes.

Banger, congrats

No haskell? Uncle you make me sad.