Goodbye, Clean Code (2020)
overreacted.io
Goodbye, Clean Code (2020)
1–10 of 224 posts
Re: Goodbye, Clean Code (2020)
#2The famous book about Clean Code was a big Oxymoron, because the examples in it pages was in Java.
Re: Goodbye, Clean Code (2020)
#3This article really buries the most important lesson about refactoring:
> I didn’t talk to the person who wrote it. I rewrote the code and checked it in without their input. Even if it was an improvement (which I don’t believe anymore), this is a terrible way to go about it. A healthy engineering team is constantly building trust. Rewriting your teammate’s code without a discussion is a huge blow to your ability to effectively collaborate on a codebase together.
Also (2020).
Re: Goodbye, Clean Code (2020)
#4This blog is essentially a journey of self discovery arriving at https://sandimetz.com/blog/2016/1/20/the-wrong-abstraction
"duplication is far cheaper than the wrong abstraction."
Re: Goodbye, Clean Code (2020)
#5The famous book about Clean Code was a big Oxymoron, because the examples in it pages was in Java.
I work with clean java, and it's a charm!
Re: Goodbye, Clean Code (2020)
#6The famous book about Clean Code was a big Oxymoron, because the examples in it pages was in Java.
As a one time java dev, I see what you are saying, but modern java is ok. Nowadays, its more on the dev team than the language.
Re: Goodbye, Clean Code (2020)
#7This is why I tend to avoid refactoring code as often I find just having a common pattern in code that's been adopted either officially or unofficially by the dev team being more important than trying to 'clean it up.' Sure, I say delete commented out code since we have git and other VCS today that makes this habit unnecessary but if a piece of code doesn't use LINQ style queries to parse lists and uses for loops instead, I just leave it be.
Re: Goodbye, Clean Code (2020)
#8That was a great article!
I really appreciate it, when people write from hard-won personal experience.
For myself, I write in Swift, and it’s quite possible to write totally inscrutable code in Swift. I am guilty of making code harder to read, and less grokkable, in my “cleanup” sweeps.
I am currently doing a bit of navel-gazing, on this very topic. I have gotten into the habit of writing very “swifty” code, and am thinking that I should probably back off a bit from that.
Re: Goodbye, Clean Code (2020)
#9[deleted]
Re: Goodbye, Clean Code (2020)
#10There was a discussion a couple of years ago on this article with 500+ comments, for those interested: https://news.ycombinator.com/item?id=22022466