46 ms·
While I don’t disagree that in the end, the only meaningful measurement is business value, I’m not sure it’s fair to put the value of John’s implemented feature
by wodenokoto 2y ago
While I don’t disagree that in the end, the only meaningful measurement is business value, I’m not sure it’s fair to put the value of John’s implemented features against the value of mine. Neither me, nor John had very much say in which feature we get to implement (assuming we are both, say frontend developers. Might make more sense if John is in devops)
Those decisions are usually decided from higher up than developers.
Maybe John got the job of fixing the advertising embed code in the html template, because he’s a junior and its basically just copy paste from the documentation and since all revenue come from ads, he is now responsible for the most valuable feature.
- Juliate 2y ago> the only meaningful measurement is business value That's true for the business. But the business is not always the unique and only incentive in work, generally speaking. > Those decisions are usually decided from higher up than developers. This depends a lot on the team structure and culture and size you are in. My first 5 years as a junior developer in a ~100 people software company, a LOT was up to developers/sysadmin left alone to design, triage, prioritise and deliver too without the supervision of a product owner or manager (which was the CTO, the role/concept of architect/PM/PO did not really exist in that environment at the time - circa 2004). I have never felt as productive and fulfilled, neither have been in a similarly fluid and flowing project since then. Sure we delivered. The company still went down for unrelated reasons. So was it productive really? In retrospect, 20 years later, what would have been really more productive (both tech-wise and business-wise)? Spinning off 3/4 internal technologies into collaborative, but dedicated small startups.