A clever code that works but is difficult to understand or a well written commented code that’s easy to understand but does not work ?

Comment below:

If you're doing something clever with the code that's not very intuitive but haven't commented it then that makes you an asshole.

But if it doesn't work it's useless, unless you want to say that not doing its job is a feature and not a bug.

Useless code is the worst imo.

@halfflat You inspired me to make the fastest function: void fast(){}

If it doesn't work, remove it.

Difficult to understand is something that can be changed.

Document, simplify or add tests for clarification and add a hint regarding the tests to the documentation.
L

Define "clever"

for(; iptrs < end; (*float)*(iptrs++) += 10.0);

@12bitfloat Egads! I cannot un-see!

YouTube uncle Bob / clean code.

This comes up somewhere in part 1.

This feeling when you have deployment on Monday, tests isn't finished on Friday and you haven't approvals. Saturday evening, you've got approval but in common way you shouldn't read your company email during weekend...

No profits...

Ehhh... Sometimes I think that client sucks :/