Product Manager: 100% useful. having a layer between engineering and the stakeholders allows the engineers to actually focus on their work. I know the product managers I work with never get a break, I have the utmost respect for them.
Researcher: this really should be lumped in with product manager. if there needs to be two product managers, so be it, but this doesn't deserve its own position.
Designer: I assume this is short for ux designer. these can be very useful on certain projects, but lightweight projects don't need them.
Contributor: anyone who has this as their job title is definitely not doing anything useful.
Maintainer: should be lumped in with developer. there's no reason to have this as a separate job from developer or engineer.
Developer: without this position, nothing gets built.
The reason it is separate is because they gatekeep what can be merged in to the release branch. A free for all with every developer having this power would quickly be destroyed by bad actors.
Edit: maintainers are "super-developers" like lead developer etc.
I am going to press X to doubt on that given the quality of UX design over the last decade or so. I also think more projects need them but don't get them as a cost cutting measure or as an outright design or project management failure.
I had a PMP at one point. Product management definitely can be a significant asset. If done correctly.
Most of the time in my experience it's a fail upward position who spends more time crying at you about why one of the marks on the online training spreadsheet is red instead of listening to the people telling him to buy new parts instead of refurbished crap from overseas so that the damn thing can actually run for two weeks in a row without blowing up.
Product Manager: 100% useful. having a layer between engineering and the stakeholders allows the engineers to actually focus on their work. I know the product managers I work with never get a break, I have the utmost respect for them.
Researcher: this really should be lumped in with product manager. if there needs to be two product managers, so be it, but this doesn't deserve its own position.
Designer: I assume this is short for ux designer. these can be very useful on certain projects, but lightweight projects don't need them.
Contributor: anyone who has this as their job title is definitely not doing anything useful.
Maintainer: should be lumped in with developer. there's no reason to have this as a separate job from developer or engineer.
Developer: without this position, nothing gets built.
So which one is the tranny who does nothing but write "codes of conduct" and try to purge productive people?
Contributer.
They contribute financial waste and a toxic work environment.
HR
The reason it is separate is because they gatekeep what can be merged in to the release branch. A free for all with every developer having this power would quickly be destroyed by bad actors.
Edit: maintainers are "super-developers" like lead developer etc.
I am going to press X to doubt on that given the quality of UX design over the last decade or so. I also think more projects need them but don't get them as a cost cutting measure or as an outright design or project management failure.
I had a PMP at one point. Product management definitely can be a significant asset. If done correctly.
Most of the time in my experience it's a fail upward position who spends more time crying at you about why one of the marks on the online training spreadsheet is red instead of listening to the people telling him to buy new parts instead of refurbished crap from overseas so that the damn thing can actually run for two weeks in a row without blowing up.
corpo artists face the wall
Is this about the pajeets spamming some big-name OSS with readme.md spam?
https://github.com/expressjs/express/pulls?q=is%3Apr+is%3Aclosed