I mean I like what is at the core of his suggestions. If you don’t take it as a religion but add a dash of flexibility on it then I think it is quite useful.
This is the way. There’s some good advice but it’s not universally applicable. The problem is, Uncle Bob defends his philosophy as if it was, diminishing the advice’s reputation.
I’d appreciate some qualification on “widely reputed” + “as much.” I’d concede it’s common knowledge that dogmatically following his advice is a mistake, but I’m surprised by the claim that his advice is mostly harmful.
Please don’t, at least at the beginning, Uncle Bob is widely reputed to have done as much harm with his OOP work as he has done good, if not more.
I mean I like what is at the core of his suggestions. If you don’t take it as a religion but add a dash of flexibility on it then I think it is quite useful.
This is the way. There’s some good advice but it’s not universally applicable. The problem is, Uncle Bob defends his philosophy as if it was, diminishing the advice’s reputation.
Look don’t be dogmatic with anything. Read it. Understand everyone has opinions. There are tradeoffs for every engineering decision. EVERY decision.
Learn to weigh them yourself and learn the intricacies of where it doesn’t make sense and where it does
I haven’t heard any criticisms. What did he do that’s wrong?
His book gave me polio!
I’d appreciate some qualification on “widely reputed” + “as much.” I’d concede it’s common knowledge that dogmatically following his advice is a mistake, but I’m surprised by the claim that his advice is mostly harmful.