|
|
|
|
|
by captainmuon
1835 days ago
|
|
I guess the problem are not managers per se, but non-technical managers. Somehow it is OK to have a pure salesperson / MBA manage engineers, but you would never put a developer in charge of the sales department. I think many developers (not just coders, but in general technical people who make the actual product, designers, engineers, ...) feel there is an unfair primacy of managers / business people over developers / technical people. This is even reflected in the job descriptions: I hate the term "individual contributor" for example, it implies replacability and that non-ICs (managers) contribute more than one person. Not every company has "bullshit" managers and for sure some developers are delusional. But these bullshit managers exist, and I believe this happens when you put people who are far away from making the product in charge. If the managers and executives are not intimately familiar with the product and the customers, then the product becomes some interchangable thing that you hustle. This can be disastrous for the work climate but also for the success of the company. |
|
If you look at a lot of pretty incredible projects that often were finished ahead of schedule or with groundbreaking capability, they often happen to be led by a deeply technical person. e.g. Hoover Dam, the SR-71, etc.
If you look at CEOs of tech companies, I believe a majority of them have an engineering undergrad degree of some form.