3 ms·
What about: - "Requirements" that don't mean anything and change on a whim - Project management and issue tracking that is nothing more than a pretend game pl
by mrguyorama 2y ago
What about:
- "Requirements" that don't mean anything and change on a whim
- Project management and issue tracking that is nothing more than a pretend game played for pretend by everyone involved yet is more important than actual results
- "We should do X" for two years, but we are still for some reason doing Y
- I'm tired of sprinting
- Incompetent managers that take a team of reasonably competent and intelligent software engineers and turn them into a void of non-productivity, where you send requirements and requests to simply vanish and never result in anything.
- A devops department that is chock full of talented individuals who are helpful and friendly and yet still take 2 weeks to turn around "Hey can you click the button in AWS to provision a new instance?"
- Knowing that this company that purposely hires middle tier talent (which I'm actually okay with, C students still build most of the world) and can't get out of it's own way still manages to run the entire industry, own the vast majority of the market, and basically takes it's profit as a tax on every consumer, and will never have to change.
- happymellon 2y ago> I'm tired of sprinting Completely agree. Its just a logical segment of time to cut up and review at the end of each segment. Even just better phrasing could help here like a "phase".