Code should be CODE: "Clean, Optimized, Documented, Efficient".
Just curious. How is optimized different from efficient
It's a bad word choice, but fitting it into an acronym is more important than giving good advice
Don't write clean code, write CRISP code
21–30 of 170 posts
Re: Don't write clean code, write CRISP code
#22Code should be CODE: "Clean, Optimized, Documented, Efficient".
Just curious. How is optimized different from efficient
Probably he was just fishing for adjectives, but generally, optimization just just the minimization of any function. Efficiency could be the minimization of a function describing resource usage.
In the real world, in real time systems one often optimizes for low jitter, which is often not contradictory to optimizing for efficiency, as one may reserve resources to keep them available in order to process requests faster, even though they're not required.
Re: Don't write clean code, write CRISP code
#23Don't follow the concrete practices in the best-selling book* vetted by industry leaders for years, instead follow this set of 5 high level goals that I've generally described and grouped together into a catchy acronym. Yay me!
* - Granted the book was written by an asshole.
Re: Don't write clean code, write CRISP code
#24Don't follow the concrete practices in the best-selling book* vetted by industry leaders for years, instead follow this set of 5 high level goals that I've generally described and grouped together into a catchy acronym. Yay me! * - Granted the book was written by an asshole.
Could you elaborate on the last point?
Re: Don't write clean code, write CRISP code
#25Ok.
* starts writing CRISP code *
Re: Don't write clean code, write CRISP code
#26If you could just write good code that would be fine.
Re: Don't write clean code, write CRISP code
#27i just try to write code that can be deleted later
the sooner the better
Re: Don't write clean code, write CRISP code
#28Since 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…
I‘d like to extend it to SIMPLED:
D - Duplicated: it's always good to have backup code at hand.
Re: Don't write clean code, write CRISP code
#29Don't follow the concrete practices in the best-selling book* vetted by industry leaders for years, instead follow this set of 5 high level goals that I've generally described and grouped together into a catchy acronym. Yay me! * - Granted the book was written by an asshole.
Could you elaborate on the last point?
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.
Re: Don't write clean code, write CRISP code
#30Very often it's the design pattern people that make code unreadable.