Hacker News new | ask | show | jobs
by virgilp 3050 days ago
> I'm talking about completed, tested, accepted features, as defined by our project teams.

Still rather strange metrics for productivity in a senior engineer. This is more what I'm taking about: https://zef.me/the-100x-engineer-6d50a690a866

If you're really senior, you shouldn't be working on the kind of features that get delivered at a rate of "5 per sprint". More like on stuff that gets delivered once every year. The junior SHOULD outperform you in "code produced" - they just shouldn't outperform you in dollars produced (or saved).

1 comments

You do what your team and company needs. If they need me to work on a big re-engineering project, or build a core framework feature, I do it. If they need me to get onto a regular sprint team for a while and churn out the backlog, I do it.