Goodbye, Clean Code — Overreacted


117 bookmarks. First posted by sledsworth 11 days ago.


via Pocket - Goodbye, Clean Code - Added January 20, 2020 at 09:43AM
short 
yesterday by mikele
Let clean code guide you. Then let it go.
programming  clean 
2 days ago by nicolas
I've killed plenty of refactors - one of the more memorable ones took two days full time to implement and test (it worked) before I deleted the whole thing w/o ever checking it in. It: 1. gave less flexibility and 2. had equivalent line counts. I admit, his "fix" made me wince more than his description of the original code; which still made me wince.
My rule of thumb is, any refactor must save (reduce) lines of code. It must be done with a reason as well. Changes are not bad, and refactoring is not bad. Sometimes, code needs to be refactored to add features. If the code is small and compact, this is easy - even if the whole has to be rewritten to accomodate the changes. If the code is complicated or large... Good luck friend!
Modularity is a key principle to keep code small and compact. Properly deciding where interface boundaries should be, and having the (accurate) confidence to move them during refactoring is also important. My rule of thumb for module/file size is 30-800 lines. Less (especially in languages w/mandatory boilerplate!) means it should go somewhere else. More, and it can probably be split into two. (Ideally it'll split earlier, but finding good fracture points can be a challenge).
Ultimately, code does need to ship. However, code also needs to be debugged, fixed, improved, and maintained. About 80% of the time is spent on code after release, so it's worth a bit of extra work to do it better - just so long as it is better (toss rewrites which aren't).
Disclaimer: I've never read "Clean Code", though I do have 12 years of industry experience, mostly as a senior or lead programmer. (It's not much fun to be the "senior" programmer with 1 year of work experience and a pair of degrees...).
todo  article  myself  comment 
2 days ago by iiridayn
Once we learn how to create abstractions, it is tempting to get high on that ability, and pull abstractions out of thin air whenever we see repetitive code. After a few years of coding, we see repetition everywhere — and abstracting is our new superpower. If someone tells us that abstraction is a virtue, we’ll eat it. And we’ll start judging other people for not worshipping “cleanliness”.
programming  code  development 
3 days ago by rmohns
It was a late evening. My colleague has just checked in the code that they’ve been writing all week. We were working on a graphics editor canvas, and they implemented the ability to resize shapes like rectangles and ovals by dragging small handles at their edges.
Archive  management 
3 days ago by ronert
Let clean code guide you. Then let it go.
programming  good-practices 
4 days ago by pmigdal
It was a late evening. My colleague has just checked in the code that they’ve been writing all week. We were working on a graphics editor canvas, and they…
from instapaper
4 days ago by nvln
Coding is a journey. Think how far you came from your first line of code to where you are now. I reckon it was a joy to see for the first time how extracting a function or refactoring a class can make convoluted code simple. If you find pride in your craft, it is tempting to pursue cleanliness in code. Do it for a while.

But don’t stop there. Don’t be a clean code zealot. Clean code is not a goal. It’s an attempt to make some sense out of the immense complexity of systems we’re dealing with. It’s a defense mechanism when you’re not yet sure how a change would affect the codebase but you need guidance in a sea of unknowns.
2020-programming-reading  tumblr 
5 days ago by pixelpaperyarn
Let clean code guide you. Then let it go.
code  development  programming  clean-code 
6 days ago by arobinski
Let clean code guide you. Then let it go.
programming  code  development 
7 days ago by tedw
can correspond to Dreyfus model of Expert -> rules can be broken
from twitter
8 days ago by jackysee
「さよならクリーンコード」。チームにおいては,クリーンコードを強要することはしばしば悪で,話し合い,直させ,文化を共有することが大事なんだね。
from twitter_favs
8 days ago by ocelot
> Don't be a clean code zealot.
software-engineering 
8 days ago by FND
👉🏻 “Goodbye, Clean Code”

🔗
from twitter_favs
8 days ago by p3k
👉🏻 “Goodbye, Clean Code”

🔗
from twitter_favs
8 days ago by piotrlewandowski
👉🏻 “Goodbye, Clean Code”

🔗
from twitter
8 days ago by codepo8
The Next Morning... did not go as expected. My boss invited me for a one-on-one chat where they politely asked me to revert my change. I was aghast. The old code was a mess, and mine was clean! I begrudgingly complied, but it took me years to see they were right.
overengineering 
9 days ago by JohnDeHope3
It was a late evening. My colleague has just checked in the code that they’ve been writing all week. We were working on a graphics editor canvas, and they…
from instapaper
9 days ago by adamlogic
Let clean code guide you. Then let it go.
programming  code-quality 
9 days ago by dbe
Let clean code guide you. Then let it go.
9 days ago by mamuso
Goodbye, Clean Code via Instapaper https://ift.tt/37YGLOQ
IFTTT  Instapaper 
10 days ago by bishbashbosh
"Don’t be a clean code zealot. Clean code is not a goal. It’s an attempt to make some sense out of the immense complexity of systems we’re dealing with. It’s a defense mechanism when you’re not yet sure how a change would affect the codebase but you need guidance in a sea of unknows.

Let clean code guide you. Then let it go."
tech  architecture  design  programming 
10 days ago by egrajeda
It was a late evening. My colleague has just checked in the code that they’ve been writing all week. We were working on a graphics editor canvas, and they implemented the ability to resize shapes like rectangles and ovals by dragging small handles at their edges.
IFTTT  Pocket 
10 days ago by deepblue
RT dev_philly : 레딧이랑 HN에서 화제가 된 글 Goodbye, Clean Code http://bit.ly/35IkJhG January 12, 2020 at 04:34PM http://twitter.com/dev_philly/status/1216262158750646272
IFTTT  Twitter  ththlink 
10 days ago by seoulrain
It was a late evening. My colleague has just checked in the code that they’ve been writing all week. We were working on a graphics editor canvas, and they…
instapaper  from instapaper
10 days ago by hskf
RT : ⚛️📝 New on Overreacted: Goodbye, Clean Code
from twitter
10 days ago by Rude
It was a late evening. My colleague has just checked in the code that they’ve been writing all week. We were working on a graphics editor canvas, and they implemented the ability to resize shapes like rectangles and ovals by dragging small handles at their edges.
Archive 
11 days ago by beergeek
⚛️📝 New on Overreacted: Goodbye, Clean Code https://t.co/duWsaj0OCd
from instapaper
11 days ago by aviflax
It was a late evening. My colleague has just checked in the code that they’ve been writing all week. We were working on a graphics editor canvas, and they implemented the ability to resize shapes like rectangles and ovals by dragging small handles at their edges. via Pocket
IFTTT  Pocket 
11 days ago by cijanzen
It was a late evening. My colleague has just checked in the code that they’ve been writing all week. We were working on a graphics editor canvas, and they implemented the ability to resize shapes like rectangles and ovals by dragging small handles at their edges.
Archive 
11 days ago by pesche
Let clean code guide you. Then let it go.
cleancode  duplication  removal  criticism  limit 
11 days ago by gilberto5757
Slavishly removing duplicate code isn't always desirable
programming 
11 days ago by jhealy
Obsessing with “clean code” and removing duplication is a phase many of us go through. When we don’t feel confident in our code, it is tempting to attach our sense of self-worth and professional pride to something that can be measured. A set of strict lint rules, a naming schema, a file structure, a lack of duplication.
11 days ago by sharon_howard
Goodbye, Clean Code
from twitter
11 days ago by nicola