11–20 of 249 posts
https://archive.is/3MbI7 (the site blocks ad-blockers, so ad-blocker users might find this URL helpful)
> An error occurred during a connection to archive.is. Cannot communicate securely with peer: no common encryption algorithm(s).
> Error code: SSL_ERROR_NO_CYPHER_OVERLAP
The older I get the more appalled I am at what managers are bringing to the table versus senior engineers.
However, the Principal (senior) Engineer I work with can be a bit of an angry ass sometimes and I am unsure he would make a good manager.
I thought this article might have been on bullshit jobs in the tech industry but it's not. Are their bullshit jobs in the tech industry?
If someone is being paid more, this person has to work more, I have seen so many people becoming managers just to actually avoid work, or thinking that tech is too hard and too much to study. So they instead go to a whole different area where most of your previous knowledge won't be required anymore, and they don't think that they are starting from zero, so they just don't study and read 2 blog articles and think that they got how is to work with people.
The older I get the more appalled I am at what managers are bringing to the table versus senior engineers.
What I noticed in my org, are the senior managers are the ones who get to talk to the business people and get to muddle the waters and do a lot of repetitive work.
Sometimes things do not get done until a project manager or senior dev actually talks to the business person and gets the correct requirements out.
I don't know why it is this way at my org, but the IT director does not want to talk to PMs, Devs, or Analysts. He would rather have a top level circle of senior managers who insulate him from the actual work.
Why do we expect to have good managers when we promote based on technical competency rather than leadership ability? Sure, a certain basic level of technical competency is needed, but after that management and development require different skills.
If you're stuck in a situation where you're not getting great feedback on what to work on, that seems like a great time to just build things and experiment on your own. Do it within the rails of the corporate environment you're in, or hell do it outside and put that energy into something else. Just because someone doesn't provide a map, doesn't mean you can't escape the labyrinth and get creative.
Just a reminder that lazy managers are the source of burnout for those who are under them. As a manager I can say, there is no easier job than just forwarding requests from directors directly to developers, not planning, and promising crazy deadlines to avoid conflict with higher management. If someone is being paid more, this person has to work more, I have seen so many people becoming managers just to actually avoi…
In my experience, pay rarely has any kind of correlation to the amount of work being done. I see it merely as a pay for responsibility for the work of those under you or, more succinctly, "being paid to throw yourself under the bus in lieu of anyone you're managing".