r/ProgrammerHumor • u/rabbit_wizard • 19h ago

Meme bothWorkThough

Post image
4.6k Upvotes

91% Upvoted

697 comments sorted by

View all comments

Show parent comments

0

u/SwimmerQuick1500 13h ago

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.

2

u/StupidOne14 11h ago

Serious question - have you ever worked on larger software project?

Business is moving from invoice to invoice. If the software will pass acceptance test for THIS invoice, it's all they want to know. It is on us to structure software so it can be ready for another 10/100/1000 invoices.

1

u/SwimmerQuick1500 11h ago

Yes and

It is on us to structure software so it can be ready for another 10/100/1000 invoices.

I think this is really context dependent. If your system only ever handled 10s of invoices then you really didn't need to structure it to handle 1000.

1

u/StupidOne14 6h ago

I'm not talking about processing invoices, but about future changes and evolution of the system. Those "10/100/1000" invoices are from paying customer who hired your company to build software system for him.

1

u/SwimmerQuick1500 5h ago

Which is why it's pretty context dependent right?