>An engineer who has appreciation for the art of the discipline.
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.
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.