This is an interesting article. I would add one more example of engineering supremacy: when engineers engage in “not invented here” activities at a great opportunity cost to the company. If your IT department is building their own key-value store deflecting any scrutiny by appealing to their technical knowledge then that’s a problem.
What this piece doesn’t touch on is why engineers might get frustrated with sales and marketing. Often it’s not because they think they know better, but because the over-promising of salespeople is causing them hardship. Also developers can immediately tell when feature work is brought into scope not because it is profitable for the company to do so, but because it will help someone higher up or a PM with their next promotion or will be a nice item on their resume. Working on these features can be very disillusioning and breeds resentment towards the folks in other roles driving it
I'm starting to realize that every company I've worked for has had a real lack of technical leadership for one reason or another.
I think that's the part that is making me resentful of sales and business types, especially as I become more experienced and higher up in development.
People who make a lot more money than me coming with wish lists and deadlines, pitching buzzwords and pretending to technical knowledge they don't have.
What this piece doesn’t touch on is why engineers might get frustrated with sales and marketing. Often it’s not because they think they know better, but because the over-promising of salespeople is causing them hardship. Also developers can immediately tell when feature work is brought into scope not because it is profitable for the company to do so, but because it will help someone higher up or a PM with their next promotion or will be a nice item on their resume. Working on these features can be very disillusioning and breeds resentment towards the folks in other roles driving it