mo1ok
Joined 12 years ago
Joined 12 years ago
Even for a standard engineer, think how many you know can code well, be leaders, AND can write good documentation.
For most things, it's always a "pick 2 out of 3" situation.
I would argue that this is the problem unto itself. The idea that a manager can work invisibly "behind the scenes" to create these conditions is the squarest negative stereotype of the MBA - that they are clerical, remote, number-crunchers who don't have an intuitive human grasp of the unique challenges their teams face, because they lack experience where the rubber meets of the road of their organization. I think this Boeing case conforms to this stereotype, as does my personal experience.
But I don't believe they're a scourge, or anything. I quantified it with "a lot" but not "most" ;)
1. Meetings to "align"
2. Cracking the whip.
That's it. That's all they have. They have poor insight into creating team chemistry, culture, focused work environments, mentorship, long-term planning, QA processes, sourcing efficiency feedback, etc. - all those things that are crucial to boosting productivity and creating supersonic teams. The people that really know their stuff and can work miracles are people that have been in the trenches for 20 years, regardless of profession. And they hands-down make the best managers.
That's my honest 2 cents, it's a bit of disgruntlement from working in large enterprise environments with engineering and technology.
Working prototypes trump all theory.
I heard all silicon valley gurus stating they were "bearish on VR, bullish on "AR". This proliferated as a mantra throughout the industry. I thought they were wrong then, and believed the opposite - because I had a working VR headset that was awesome, but had only heard somewhat meh things about existing AR prototypes.
Until great AR hardware comes out, I'm still sticking with the same opinion.
A parallel problem is immigration and, as the top comment pointed out, cheap credit encouraging vacancy.