It's one thing to use a software career to explore the things that give you joy. Building software is fun. But it's another thing to use it to run away from things you're intimidated by, like interacting with other people or empathizing with them. "I got into software so I wouldn't have to deal with people" is a joke, but it's not really a realistic way of approaching the world beyond the very junior level.
You can either rant about how people should be or meet them as they actually are.
You can have pretty normal temperament and be a decent engineer, but if you aren't positive 110% of the time, always sucking up to management, always accepting more work, always subtly gaming those around you, then apparently you're a "bad engineer" for not understanding the "business". I might be crazy but that shit is not normal. Go play the game if you want to but it is not normal.
Charisma isn't lying or being sensitive, so you aren't opposed to it.
My takeaway is to ignore the title and per the text, be able to work with other engineers (play well with others). That means speaking their language and being able to relate to others, both with technical precision as warranted, and with human/emotive understanding. To remember that it's not about you, it's about the team/org. To keep in mind principles such as "assume good intent". etc.
Now, it does so happen that most orgs are dysfunctional so being successful at that more "human" / relatability part does mean being successfully dysfunctional. Sadly. Author does live in his utopian world and the blog is titled as such.
It’s harder for many engineers to be outcome focus (what non engineers care about “business value”) and work backwards without getting into the weeds. Engineers usually think in terms of process.
Engineers are also more pessimistic thinking about all of the things that can go wrong and non engineers are usually more optimistic seeing everything that is possible. I’m not passing judgment on either.
The “Geek Leader’s Handbook” (https://www.slideshare.net/CommunicationCoach/the-geeks-guid...) and my pass Amazon indoctrination of “Working Backwards” helped me a lot.
Yes, tech companies have become more about ladders, optics, proxy metrics, performance review than about building, experimenting, leading with technical skill.
This happens because tech got infected with corpo MBA-style practices. Obviously, not a thriving environment for innovators. Great environment for corporate leeches who themselves can't do anything but want to tell "others" what they should be doing.
The idea that you are either an MBA-type "politic player" with zero technical skills whatsoever, or someone doing the "real work" who is super technical but starts fopsweating at the idea of having to present their work or write something that isn't code doesn't really line up with my experience.
A sizable percentage of my managers have written code while being managers. A sizable percentage of my programming coworkers have had MBAs.
The two extremes do not last very long in any healthy organization.
Inconveniently for some software types, the world doesn't and shouldn't revolve around software development.
You should be well rounded. Managers with MBAs who work for tech companies should be able to have technical conversations, and be able to share their opinions with technical people without sounding like imbeciles. Software engineers should be able to understand and discuss business considerations without sounding like it is beneath them, or similarly sounding like they think the money just appears in the bank account magically.
The healthiest organizations promote this multidisciplinary approach, they invest in their employees to help make it happen, and most importantly and perhaps most controversially, if you're not well rounded and knowledgable about all aspects of the business it is extremely career-limiting beyond the lowest levels of management or whatever the terminal IC role is in the org.
Sounds great. Except.. if you're advocating for "charisma" in the first place, then that's probably not really the goal and definitely not the effect that you'll see. Hence the various cranky/skeptical/cynical comments in this thread. There's plenty of charisma in tech already, and it's usually associated with fraudsters like SBF.
No one's blaming MBA. In fact, if the corpo MBA people actually focused on - generate revenue in order to pay your salary, pay the bills, and give a dividend to its shareholders - that'd be great. Use some skill to generate these.
But corpo MBAs spend an enormous amount of time in ladder-climbing, promos, hirings, firings, reorgs - all of which are orthogonal to the points you described earlier: generate revenue in order to pay your salary, pay the bills, and give a dividend to its shareholders.
TL;DR corpo MBA are not doing what is required of them. Instead, they are sucking on innovators with corpo policies - leading to the original post.
Making the machine run better and more efficiently is how they generate revenue in order to pay your salary, pay the bills, and give a dividend to the shareholders. It's the test automation of the business world.
This is exactly corpo MBA-style which is orthogonal to innovation. By stating this statement, you just contradicted your own point earlier about why corpo MBAs are needed.
I hate to break it to you - you ARE the typical corpo MBA who will shift goalposts to justify your own position - and it is very evident to anyone engaging in a discussion with you.
Only sub par engineers need to constantly be politely told they suck and have to sugar coat everything for them. Good engineers come up with good ideas, at least good at a foundational level, where you can discuss the pros and cons. If an idea has some legitimate merit but a drawback you don't think is worth it, then the criticisms are real and honest, no ones feelings are getting hurt.