An engineer who has appreciation for the art of the discipline. But since you don't value that and think that engineer is a spoiled brat, you won't hire him.
That' sounds incredibly vague and useless. The problem is always communicating to management the value add of such a position. If they see money gets made without it, than why bother? The customers don't complain so it's a slam dunk. And most companies are customer focused.
>But since you don't value that and think that engineer is a spoiled brat, you won't hire him.
Like I said, the issue is budgets. Not every company is big-tech and can afford lavish salaries to attract SW shamans to bless your codebase with their appreciation for the craft. Most SW is a commodity, not an art. Some is, sure, but that's cherry-picking.
Who defines what "high quality code" is and who enforces it in a team? Because what's high quality to you might not scan to other members of the team, and if you want to your standards across the team then you have to spend time and effort educating the people and enforcing the standards. And now you're wasting time obsessing over standards and guidelines while your efficiency doesn't increase.
> you can just be better
Better how?
>The best places get a ton done with very few people.
Is it because the quality of their code, or because those people are better at what they do and better at working as a team?
>And they're not doing this by slinging crap code at the wall as fast as they can!
Because they're a highly specialized company making a highly niche product who's features must include high tolerance and availability ahead of new features. You can't in good faith compare trading firms to your average web dev shop. different projects, different customers, different budgets and profit margins.
That's like comparing an F1 car to a road car and telling the engineers working on the road cars to "just be better", that the reason their work is not matching the F1 car is the quality of their drafting and not the 100x difference in budget and requirements.
Edit to reply here to your child comment below:
>If you have a strong team, you don't have to "enforce" quality.
Obviously you can do a lot with fewer people when you have crazy money and therefore can afford very high hiring bar. That's not most companies and not most SW projects though.
Hence my original comment: "I think people focusing on SW engineering being art have been spoiled by only working at companies with infinite money, like Google"
Your point only works if you cherry-pick well funded big-tech like XTX, but once you step out of that bubble to non-tech companies who need SW products on smaller budgets things are way different. Those places don't have the hiring bar of XTS, so the quality will be different.