267

visual coding rule (lemmy.blahaj.zone)

submitted 6 months ago by paris@lemmy.blahaj.zone to c/196@lemmy.blahaj.zone

55 comments fedilink hide all child comments

https://twitter.com/b0tster/status/1744529728680161615

you are viewing a single comment's thread
view the rest of the comments

[-] neonred@lemmy.world 22 points 6 months ago* (last edited 6 months ago)

If you do any code work, read this:

Robert C. Martin - Clean Code

[-] Vulwsztyn@lemmy.world 17 points 6 months ago

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.

[-] netwren@lemmy.world 6 points 6 months ago

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

[-] iAvicenna@lemmy.world 6 points 6 months ago

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.

[-] BiteSizedZeitGeist@lemmy.world 4 points 6 months ago

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.

[-] Shyfer@ttrpg.network 5 points 6 months ago

I haven't heard any criticisms. What did he do that's wrong?

[-] Thcdenton@lemmy.world 1 points 5 months ago

His book gave me polio!

[-] kogasa@programming.dev 1 points 5 months ago

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.