3 ms·
I didn't say they were the same job. I said they were accorded different levels of respect and prestige, which is what this post is about. I didn't want to be a
by nilkn 10y ago
I didn't say they were the same job. I said they were accorded different levels of respect and prestige, which is what this post is about. I didn't want to be a pure executive or manager.
At that company, it was, frankly, impossible for a developer to get the same perks as a manager. I'm sure there are companies out there that handle this a lot better and don't make management the only path to promotion. These have just been the minority in my personal experience.
---
I also agree with you for what it's worth that management is a skill in and of itself that most developers wouldn't be good at. The point I was making in my previous post was a little more nuanced. Think of it like this. At a large company, there might be 100 VPs who are pure managers, and there might be 5 very distinguished engineers who are at the same VP level. This creates the impression that developers can rise up just as high in the company, when in reality it's more of an illusion. The technical skill level necessary to reach VP level as a developer is astronomically high. The management skill level necessary to reach VP level as a pure manager is certainly not low by any means, but it's comparatively much lower than it is for VP engineers.
- k-mcgrady 10y agoThanks for the clarifications.
- pkaye 10y agoOne thing that helps is to get to personally know the people up the management chain better. Respect comes easier when they know you as a person instead of just a name on a document. I learned this the easy way at a company when our manager left and it took a long time to find a replacement so all the directors and VPs would come directly to us for questions, advice, etc.