Hacker News Reader

Comment by majewsky | Hacker News Reader

It's sad that this gets downvoted, because it's the only realistic approach in such a situation (which is also sad).

I've seen a lot of teams in a lot of organizations, both bad and good.

Good teams cheat in bad organizations. That's why they're good teams. Whatever your metric, code quality, quality of life, being kind and supportive -- in organizations that pervasively do it bad, good teams cheat in order to do it well.

I think the trick is that only a small group of people know that they cheat, otherwise some mid-level manager would come down on them, hard.

Yes, I don't see this a problem, normally releases get delayed, if you get more time to develop better, then why not? I always saw testers talking with product owners and managers about one or other developer that was slower but had delivered less defect.

I know that feeling. I'm one of those developers that is slower than a lot, but I also know from long experience that when I deliver something, it's solid. It's not that I don't make mistakes, but that I work in a way that helps to minimize them when I do make them. It takes me longer to get things done than the hotshots, but there will usually be fewer problems and the problems that do exist will usually be much shallower. And unlike a lot of people my work contributes to a net decrease of technical debt.

I'm not saying this to brag, but to emphasize that this is what it takes to do quality work.

Reply on news.ycombinator.com