Hacker News Reader

Comment by jdlshore | Hacker News Reader

I clicked the link hoping for a critique of the ideas in SOLID and Clean Code, but what I got was an ironically long-winded critique of Bob Martin’s speaking style.

Martin and I have our differences, but this article isn’t really useful. Martin has a brand and a style. A lot of people find it engaging and entertaining. If you don’t, that’s fine, there’s plenty of other ways to learn about the ideas that are more concise.

View on HN

Regardless of style, Uncle Bob's Enterprise Java Clean Code opinions are overly dogmatic and harmful in most places.

I pick and choose the bits I think make reasonable sense, an go with better options myself.

This is the right approach, unfortunately many of my coworkers in software are ridiculously dogmatic about it

If you want something real, look at Clean Code Horrible Performance youtube video if you haven't.

I also found Bob Martin entertaining, but after trying to follow his suggestions I just got into the trap that Casey Muratori shows: even if I don't care about the performance of the code at the start, the amount of abstractions Uncle Bob advises makes it just too easy to make the code extremely hard to optimize later.

https://youtu.be/tD5NrevFtbU?is=vuVfjbsINQrtfvbC

Sorry if the title mislead you. To me criticizing SOLID and Clean Code directly is like beating a dead horse, so here I wanted to criticize the way they are presented because that's a big reason why it's successful.

I found this https://vimeo.com/157708450 video quite interesting critique of SOLID.

I felt the same. Even the off topic arguments don't many sense. Some sort of weird rant about acronyms that made no sense to me. Waste of time

> [..] There’s plenty of other ways to learn about the ideas that are more concise.

Would you have any good resources to share?

I’m not really a fan of the ideas. They’re not wrong, exactly, but I think they’re overstated. Instead, here’s some alternatives:

For design, Evans’ Domain-Driven Design does a good job of representing classic object-oriented design, and Fowler’s Patterns of Enterprise Application Architecture is good for expanding past business logic to larger systems.

For coding habits, “The Pragmatic Programmer” is a classic for a reason.

Thanks for the tips!

You are not alone in his style, but in what he actually says, all of which seems to me to be wrong.

He seems to prefer being called Uncle Bob.

Reply on news.ycombinator.com