Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Don't write clean code, write CRISP code

bitfieldconsulting.com

Post reply on HN
Print view View original

131–140 of 170 posts

Re: Don't write clean code, write CRISP code

#131

Post by Symmetry »

m_mueller wrote: post #51
dkdbejwi383 wrote: post #37

DRY is probably my least favourite programming meme. There are far too many overzealous juniors who learned it and have a bee in their bonnet about creating absurd abstractions around any two lines of code (or config) that have vague or imagined similarities, locking in all sorts of annoying indirection.

Totally agreed. I've tried explain exactly this issue in a talk [1], trying to find a useful synthesis between different paradigms like KISS, DRY and YAGNI. [1] https://www.youtube.com/watch?v=0FIZn2trkoA&pp=ygUXbWljaGVsI...

I made a DRY/YAGNI yin/yang sticker for my laptop a little while ago.

https://i.redd.it/16qm2a3m7m991.jpg

Re: Don't write clean code, write CRISP code

#132

Post by riffraff »

dagw wrote: post #76
riffraff wrote: post #29

Earlier quoted context omitted.

Uncle Bob has been widely criticized for his political stances, basically being a MAGA republican. This also spilled into some critiques of Clean Code which are sometimes colored by this.

Uncle Bob has been widely criticized for his political stances, basically being a MAGA republican. I don't think that's a fair representation of his critics. I've been reading (and even occasionally writing) critiques of Uncle Bob for many years, and you are literally the first person I've ever seen even mentioning is political stance. Up until 30 seconds ago I'd not once reflected over who Uncle Bob might vote for.

But we're those critiques of him being a horrible person?

I disagree with some of his technical ideas, but that in itself would not warrant such a characterization.

Re: Don't write clean code, write CRISP code

#133

Post by commandlinefan »

BulgarianIdiot wrote: post #5

What CRISP is supposed to mean: Correct Readable Idiomatic Simple Performant Notice that all this is just well-wishing and suitably vague, so that you feel the need to buy a book & hire a consultant to explain it to you. The trick is there's nothing to explain.

> well-wishing and suitably vague

That way, no matter what you do, they can say you did it wrong, and no matter what they do, they can say it's right.

Re: Don't write clean code, write CRISP code

#134

Post by sharas- »

flippinburgers wrote: post #85
clnq wrote: post #17

Since we’re adding new backronyms every day, I propose SIMPLE. S - Spaghetti: write tapestry of code like a chef. I - Interlinked: if the project has modules, they should all depend on each other (we are strongest when we can depend on one another). M - Micromanaged: if the product owner doesn’t expect reports in the daily stand-up, do they even care? P - Perplex: diversity for the codebase. L - Lazy: Bill Gates once…

Good old Uncle Bab! Love it. I have a borderline weird hatred towards the concept of "clean architecture".

Just watch his videos on "clean code" or "Scribes Oath". You can't make this shit up. He literally glorifies tribal rituals. Calls devs - "his tribe" etc... Such zealous simpletons are a plenty in our pop culture driven industry.

Re: Don't write clean code, write CRISP code

#136

Post by marcosdumay »

DarkWiiPlayer wrote: post #99
IshKebab wrote: post #60

Earlier quoted context omitted.

I put it second behind "premature optimisation" which is used to justify never caring about performance at all (until it's too late and you can't do anything about it).

Actual premature optimisation is harmful for the same reason as premature abstraction. In both cases, improvements that come "for free" should be done without thinking, but one they start to impact readability, we should consider how beneficial those changes really are.

If you don't know what you are building, any action is premature.

Re: Don't write clean code, write CRISP code

#138

Post by dagw »

riffraff wrote: post #132
dagw wrote: post #76

Earlier quoted context omitted.

Uncle Bob has been widely criticized for his political stances, basically being a MAGA republican. I don't think that's a fair representation of his critics. I've been reading (and even occasionally writing) critiques of Uncle Bob for many years, and you are literally the first person I've ever seen even mentioning is political stance. Up until 30 seconds ago I'd not once reflected over who Uncle Bob might vote for.

But we're those critiques of him being a horrible person? I disagree with some of his technical ideas, but that in itself would not warrant such a characterization.

I have honestly never heard (or made) a critique of him as a person. In fact the little I have heard about him as a person has generally been positive.

Re: Don't write clean code, write CRISP code

#140

Post by sergiotapia »

edumucelli wrote: post #10

It is laughable talk about "Don't Repeat Yourself principle" on a strongly biased towards Golang article. A language that took 13 years to add a simple method (Index) that helped the programmer to find an element in an array (slice). Before that you had to write a for loop every time you wanted something from an array. Talk about "DRY" ... That is everything but "simple" as described in the article.

Literally why I stopped writing Go. I was going crazy repeating myself so much. If err != nil also never felt nice to use.
Post reply on HN