[diggan]

> Clearly no one stops and ask "Should we?". Which is sad.

I'm not sure, I've seen plenty of cases where programmers do stop and ask "Should we?" while management says "It's not ideal, but you have 4 hours allocated to shipping this things, so decide the "right" approach for achieving our OKRs" or similar.

[guappa]

I don't know where you've met all those programmers who are good at their job. In my experience the ones who don't care beyond the questions "does it compile? Does it pass the test suite?" outnumber the ones who ask questions like "is this even the correct approach at all?"

[diggan]

> I don't know where you've met all those programmers who are good at their job

Most of my professional experience is from working in smaller startups, grown into medium-sized ones, that I've picked to approach for work because I liked the programmers who already worked there, I'm guessing that's why :)

Consulting for various IT and IT-adjacent companies of all types of sizes, I certainly understand where you coming from, they tend to already be burned out (or something) enough to not ask questions anymore.

[simsla]

Mostly worked at bigger companies. Once joined a company with pretty shit colleagues/management. Left after three months.

If you have mobility, it's worth shopping around for a decent place to work.