4 ms·
Blaming the programmers seems misdirected; blame management, if anyone. Programmers rarely get to set the priorities or determine resource allocation.
by Nagyman 8y ago
Blaming the programmers seems misdirected; blame management, if anyone. Programmers rarely get to set the priorities or determine resource allocation.
- guntars 8y agoI think it’s fair. If the management is incompetent and keeps rushing programmers to build poorly thought out features, they’re also usually unable to evaluate the quality. The programmers on the other hand know exactly how bad the things are that they’re building and if they sign their name and say “I built this!” then it’s on them. Maybe I’ve just worked for companies where developers have a lot of say in what and how gets built.
- mgkimsal 8y ago> Maybe I’ve just worked for companies where developers have a lot of say in what and how gets built. that's probably closer to the truth. if you're large enough to have multiple teams of multiple people, in most cases, they don't all have a full view of what's going on (priorities, roadmap, feedback, etc). even if someone said "I ain't doing this!" and quits, there's no real impact. If an entire team dug in their heels on something, that might have influence, but you're getting to a situation that doesn't often happen.
- guntars 8y agoAt my current company we have 4-5 independent teams and the PMs talk among themselves and come up with the roadmap, but then they bring it to their teams and there are multiple opportunities for devs to comment or raise any objections. It was similar at my previous, much smaller company. Throwing the keyboard across the room and yelling "I QUIT!" is one way to give feedback to the management, but usually I've found that raising your hand and bringing concerns about performance or stability is enough to get people to listen since they also want to build a great product.