[xprn]

Question for the masses - is “Clean Code” still something worth reading nowadays? I have so far only heard good things about it (but that might also just be survivorship bias, I would assume books that aren’t good wouldn’t really be talked about as much), but have yet to grab a copy

[muzani]

Some parts are okay. It's one of the books that hasn't aged very well though, similar to JavaScript: The Good Parts.

A lot of it tackles flaws in Java itself, and assumes that OO in geeral has the same problems. For example passing an object instead of multiple parameters into a function. It's one of the suggestions that our team just agreed to reject for Kotlin/Dart because we could set default values.

Uncle Bob is generally one of the best in explaining why problems happen, though you have to step aside and think whether the solution he proposes is the best.

[jjice]

I wasn't a huge fan when I read it a year or two ago. It's fine, but I think that there are a lot of things that just aren't that clean (which is a subjective take). Uncle Bob in general though is a favorite of mine. Highly recommend Clean Architecture, Clean Agile, and The Clean Coder.

[scrapheap]

It's very heavily Object Oriented influenced, but it's still worth reading. Just make sure that you (and any team you work with) form your own opinions on what Clean Code is for you.