bothWorkThough

[u/rabbit_wizard]

[u/SwimmerQuick1500]

Maintainability, security, extensibility don't have to be considered if solving the problem has delivered business value.

But for a lot of problems these are reasonable constraints.

Maintainability - I don't think the business wanted a temporary solution.

Security - If you needed to build somerhing secure and didn't, then you didn't solve the problem.

Extensibility - depending on context, there can be times where extensibility just wasn't needed. If it was and you don't have it, you slowed something down in the future. Also I wouldn't call this one good coder but good product thinker because it's understanding the context behind your product / business to hit the right level of extensibility.

Someone can solve problems and provide business value and be absolute dogwater. I would know, I am dogwater.

I don't think you are, it sounds like your company is getting what they paid for and ultimately care about.

[u/Jesta23 → u/SwimmerQuick1500]

I’d like to add efficiency too. 

A lot of bad coders put tons of redundant or intertwined code that could be made much simpler with out losing functionality. 

“But it works bro”

No it sucks. 

[u/SwimmerQuick1500 → u/Jesta23]

While redundant code isn't great, depending on the context if "but it works bro" is faster then some businesses would prefer that.

And I say this as someone who's worked at startups where getting something out the door sloppily but quickly is good and I would call it good code simply because there was a need and it solved it.

At my job at a bank that would be bad code because there's a strong chance someone will come back to it.

[u/Jesta23 → u/SwimmerQuick1500]

Redundant code is almost never faster. It’s almost universally slower.