4 ms·

Really the only two dimensions that matter for development as a function are time to market at a sufficient quality, and resources needed to maintain the codeba

Really the only two dimensions that matter for development as a function are time to market at a sufficient quality, and resources needed to maintain the codebase at sufficient quality once delivered. Any metrics about individual devs needs to support one of those two group goals. The fewest lines of codes is an ok metric in that it often means more maintainable. But it can mean less maintainable if it's too cute. It's a leading indicator, but you can just directly measure bug volume and time to resolve issues. Faster code is an irrelevant distraction 90% of the time. Sister comment mentioned DORA metrics, which I wasn't familiar with and look exactly right: * Deployment Frequency: Refers to the frequency of successful software releases to production. * Lead Time for Changes: Captures the time between a code change commit and its deployable state. * Mean Time to Recovery: Measures the time between an interruption due to deployment or system failure and full recovery. * Change Failure Rate: Indicates how often a team’s changes or hotfixes lead to failures after the code has been deployed.

Maursault 4y ago
> Faster code is an irrelevant distraction 90% of the time. Time is money. Say a piece of code is executed zillions of times by hundreds of millions of customers. What would seem like a negligible increase in results, even a few milliseconds, adds up at scale. Sparing resources translates to saving money, both in energy expenditure and in squeezing in as many transactions in a minute as possible.
- drc500free 4y ago
  Most code is not executed a zillion times by hundreds of millions of customers. Most products are not concerned with squeezing in as many transactions in a minute as possible. All of those have their time and place. B2C codepaths used by all normal users in their most common daily usage? sure. HFT platform? sure. Pretty much anything else? You're probably spending more in dev salary than AWS savings and getting sniped by a competitor.
  - Maursault 4y ago
    > You're probably spending more in dev salary than AWS savings and getting sniped by a competitor. I don't doubt you, but it is asinine if dev salaries are under such oppressive scrutiny when mind-boggling amounts of spending is wasted on management and especially executive salaries. Talk about bending over a dollar to pick up a dime.

Maursault 4y ago

> Faster code is an irrelevant distraction 90% of the time. Time is money. Say a piece of code is executed zillions of times by hundreds of millions of customers. What would seem like a negligible increase in results, even a few milliseconds, adds up at scale. Sparing resources translates to saving money, both in energy expenditure and in squeezing in as many transactions in a minute as possible.

drc500free 4y ago
Most code is not executed a zillion times by hundreds of millions of customers. Most products are not concerned with squeezing in as many transactions in a minute as possible. All of those have their time and place. B2C codepaths used by all normal users in their most common daily usage? sure. HFT platform? sure. Pretty much anything else? You're probably spending more in dev salary than AWS savings and getting sniped by a competitor.
- Maursault 4y ago
  > You're probably spending more in dev salary than AWS savings and getting sniped by a competitor. I don't doubt you, but it is asinine if dev salaries are under such oppressive scrutiny when mind-boggling amounts of spending is wasted on management and especially executive salaries. Talk about bending over a dollar to pick up a dime.