Clean code is that which causes the fewest number of WTFs/minute when read 🤣
I have seen such cleanly architected code that i couldn't find the actual implementation. I have seen such spaghetti code that i might as well rewrite it. I think as long as your code is consistent and a junior can take over, you are winniing.
When I worked in a startup, the other programmers remarked at how "neat" and "easy to understand" my code was. I mean, I'm a cynical old dude, too, but it is possible to write code in the care of others.... and to have them notice.
Clean code is something I have yet to witness in my 17 years as a software developer. For me it is almost a myth or legend at this point.
Clean code is in viewer's eyes but I'd say it should not invoke the "fight or flight" feeling. Ie: 1. It's not repulsive. 2. You feel minimal to none desire to add or change something about it.
The clean code is like love. I don't know what it is but I'm sure I felt it few times.
Here's my definition of clean code 1:55 in: Clean code is code that does not fall apart, cease to work or cease to be intelligible or modifiable the moment some dirt gets thrown on it.
In Python you can avoid loop duplication by defining a generator. More elegant and easier to use than passing a lambda argument.
I always say, code should tell a story.
Hemingway's "Old Man and the Sea" should be everyone"s model for clean code.
I like to close my eyes and pretend its Vizzini from princess bride talking
"You may think that your job is to get code to work, that's not your job, that's half of your job, and it's the least important half." This statement seems so detached from the reality that exists when you just think about code. Your job is quite literally to write something that works and brings immediate value. Would love to see a company manager that tells you to go ahead and refactor your code for a month to get it into a state where it's more readable for the next person.
I dislike the term "clean code" for the same reason I dislike the term "best practices". It tends to espouse one's opinion as moral virtue. Instead of using such terms, I would prefer people spoke more along the lines of, "In my experience, here are patterns made my work experience more difficult, and here are patterns that made my work easier." That said, if I were to promote a version of "clean code", I would say, "Is it easy to read? Is it easy to debug? Is it easy to change? If so, then it is fair to say it is clean." Another way to phrase it is along the lines of the "Golden Rule": write code for others, as you would have others write code for you.
CLEAN CODE IS CODE I CAN READ.
Code is for humans. If it was for the computer, then all code would be machine code. Code is for humans. Please write code like you understand that.
Clean code is code that doesn't raise you mythos score...
If I wrote it? Clean. If I inherited it, not so much. The code itself is a MacGuffin.
Fisrt
uncle bob sucks
@bundlesofun9568