[nicexe]

I mostly agree with the points but I hard disagree with point number 3.

Clean code makes the project more easily maintainable. We generally try to keep a standard in code quality (and I would say 98% of the codebase we touch is well written). We also try to schedule refactoring rounds (but that doesn't always happen because of time constraints).

[Clubber]

He didn't say clean code was bad, he said nobody cares about your clean code. I assume he meant outside the development department.

[sanderjd]

That isn't true either though. Sure, they don't care about it as a first order thing, but they care about development not slowly grinding to a halt over time. And writing well structured code is one of the things the software side of the house does in order to do a better job delivering on that desire from the business. If nobody on the technical side has the credibility or trust to make that case, then that's a problem.

[Clubber]

>Sure, they don't care about it as a first order thing, but they care about development not slowly grinding to a halt over time.

Most only care when it affects them or sales, not when devs are asking to allot time to clean up code or pushing off a release to fix wonky stuff. In my mind that's not caring.

That's like people care that they can't walk up stairs without huffing and puffing, but not enough to actually diet and exercise. That's not actually caring, that's really regret.

I'm fortunate though, my company gives a lot of credence to dev.

[sanderjd]

That situation sounds to me like the problem of the development org not being trusted by the company's leadership when they say "this will slow down short-term initiatives but speed up long-term ones".

[Clubber]

Yes, it's pretty common in my experience. Of course executive bonuses are granted based on short-term initiatives more so than long-term ones. When they finally reap what the sow, just blame dev. You don't get to be an executive without knowing how to politic.

[sanderjd]

Oh yes, I agree it is common! But not at all universal.

[trickstra]

In the article:

> Don't get me wrong, people will expect you to write good and clean code.

I can agree with this. Clean code is not "celebrated" because it is expected as normal. You won't get a raise for it. You could get problems for not writing clean. But when the business gets into a tight spot, they will accept shitty code that fulfills their desired goal over a nice clean and elegant solution delivered few days later. In this case, the shitty code could get you a raise.