this post was submitted on 15 Mar 2024
270 points (97.5% liked)
Asklemmy
43394 readers
1544 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The project manager is your peer, not your king.
It all depends on the project and the team. On some, you work with and along the PM and all is good, and other times you get dictated unconnected requests that you need to fight or ignore.
Thankfully I've only ever worked in the first environment.
Lucky, my first 2 dev jobs had PMs that were right out of college business majors with zero web development experience. They were just direct unfiltered conduits between the clients and devs, but with a layer of telephone game and almost no ability to day no to the clients.
It was a fucking nightmare. By the time I did get a good PM, I was pretty much burned out and started my own consultancy (since Iโd been managing a small team and doing both dev and PMโs job by then anyway).