3 ms·

> We need to think about measuring productivity in a holistic and multifaceted way, not in a reductionist, unidimensional way. Accordingly, we need to measure p

> We need to think about measuring productivity in a holistic and multifaceted way, not in a reductionist, unidimensional way. Accordingly, we need to measure productivity using more than one metric, and we need frameworks for selecting metrics (for example, SPACE from Forsgren et al.) that enable us to understand tradeoffs. > We must think about productivity both in the short term and the long term; for example, we need to understand the effects that biases against underrepresented groups have on developer productivity in terms of getting code submitted and also on retaining skilled employees by treating them fairly and affording them the same opportunities that others enjoy. There's many issues with "human-centered" anything. Mostly on the idea that we "start with people", but we don't realize our own flaws as humans. Humans have finite willpower and creativity. They acknowledge that but still continue on persisting that this problem can be solved. It can't. So we're trying to measure how much we produce when we should be measuring how efficient or effective we are with that finiteness. Again, quite a relative and impossible task. The object isn't to make something (i.e. be productive). It is to be in that wonderful state in which making something is inevitable. No metric or metric framework is going to help you here. There is no single proven "artist way" to do this either. Everyone has different routines and approaches to their creative finiteness. Attrition is especially harmful at any company because you lose a flavor of creativity giving other creators perspective on how to create as budding artists. You can't really replace it easily and it takes time to mature in your talent. Personally I think chasing an answer to these problems is a fool's errand. Many before have tried and failed. Not everything in life needs to be measured or improved. Especially something like creativity where it already is pretty much magic.

celdon25 4y ago
> The object isn't to make something (i.e. be productive). It is to be in that wonderful state in which making something is inevitable. In the absence of at least some reasonable system (despite its flaws) to recognize a software engineer’s contributions, you’re likely to have a situation where the team as a whole is falling short. Managers will be under pressure to turn up the temperature on the whole team, and the environment will risk becoming more akin to a sweatshop. I’ve seen it firsthand more than once. So I’d wager the contrary to what you suggest here. The measurements are what enable management to keep some greater distance without being a distraction. Creativity might even become inevitable if the right system is in place, but such a thing is not easily accomplished no matter the approach you try. I feel that data trumps the lack of such in this case though. Though this is a nice topic for debate and I’d love to see some more literature or studies on it.
- astrobe_ 4y ago
  From a programmer's perspective, I'd say "if you want to go faster, release the brakes". So I think the first job of a manager is to "remove the brakes", which implies that they have to find where they are first. A measuring network could help here - and would less likely fall under Goodhart's law.
- sidmitra 4y ago
  I've been interested in this topic lately, given the economic outlook, which in turn is pressing more and more companies to look at impact, productivity, "doing more with less" Here's some other related links i've looked at before, but i'd be interested in gathering further research on this as well. - SPACE framework, https://queue.acm.org/detail.cfm?id=3454124 https://queue.acm.org/detail.cfm?id=3454124 - DORA metrics, https://cloud.google.com/blog/products/devops-sre/using-the-four-keys-to-measure-your-devops-performance https://cloud.google.com/blog/products/devops-sre/using-the-...
abraxas 4y ago
> The object isn't to make something (i.e. be productive). It is to be in that wonderful state in which making something is inevitable. Wow, that's so aptly put. I love seeing these pithy quotable lines on HN from time to time. Thank you.

celdon25 4y ago

> The object isn't to make something (i.e. be productive). It is to be in that wonderful state in which making something is inevitable. In the absence of at least some reasonable system (despite its flaws) to recognize a software engineer’s contributions, you’re likely to have a situation where the team as a whole is falling short. Managers will be under pressure to turn up the temperature on the whole team, and the environment will risk becoming more akin to a sweatshop. I’ve seen it firsthand more than once. So I’d wager the contrary to what you suggest here. The measurements are what enable management to keep some greater distance without being a distraction. Creativity might even become inevitable if the right system is in place, but such a thing is not easily accomplished no matter the approach you try. I feel that data trumps the lack of such in this case though. Though this is a nice topic for debate and I’d love to see some more literature or studies on it.

astrobe_ 4y ago
From a programmer's perspective, I'd say "if you want to go faster, release the brakes". So I think the first job of a manager is to "remove the brakes", which implies that they have to find where they are first. A measuring network could help here - and would less likely fall under Goodhart's law.
sidmitra 4y ago
I've been interested in this topic lately, given the economic outlook, which in turn is pressing more and more companies to look at impact, productivity, "doing more with less" Here's some other related links i've looked at before, but i'd be interested in gathering further research on this as well. - SPACE framework, https://queue.acm.org/detail.cfm?id=3454124 https://queue.acm.org/detail.cfm?id=3454124 - DORA metrics, https://cloud.google.com/blog/products/devops-sre/using-the-four-keys-to-measure-your-devops-performance https://cloud.google.com/blog/products/devops-sre/using-the-...

abraxas 4y ago

> The object isn't to make something (i.e. be productive). It is to be in that wonderful state in which making something is inevitable. Wow, that's so aptly put. I love seeing these pithy quotable lines on HN from time to time. Thank you.