this post was submitted on 13 Aug 2026
203 points (98.1% liked)

Programming

28091 readers
475 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 3 years ago
MODERATORS
 

studies show a clear trend – output is up (more code, more commits, bigger diffs), but outcomes don’t reflect that trend. If anything, the average team is taking longer to ship worse software

you are viewing a single comment's thread
view the rest of the comments
[–] Feyd@programming.dev 104 points 1 day ago (2 children)

output is up (more code, more commits, bigger diffs)

We've known measuring output by lines of code is counterproductive for a long time.

[–] jtrek@startrek.website 41 points 1 day ago (2 children)

Has management known that?

A lot of problems seem to be downstream from "management are idiots and assholes"

[–] dreamkeeper@literature.cafe 3 points 14 hours ago

At any minimally competent company they are aware.

However my company mostly has former engineers as engineering managers.

[–] Feyd@programming.dev 8 points 1 day ago (3 children)

I'm sure there were pockets but it legitimately seemed like that dragon had been slain until recently. Trying to assign more meaning to scrum points has been in vogue for a while though.

[–] jtrek@startrek.website 6 points 1 day ago (1 children)

My team assigns both hours and points to tasks. I've never seen the points used for anything but they still spend time on it.

[–] Kissaki@programming.dev 3 points 20 hours ago

That's... an interesting approach.

That battle is perpetual. Lazy management sees a number that resembles a statistic, and try to use it as an easy metric for stuff it doesn't represent. Points do aggregate into velocity, which is worth measuring. But on their own, points are a proxy for estimation in $SPRINT_LENGTH days. The way to manage up is to keep making it clear that the smallest unit of estimation in Agile is the sprint length; points are used to subdivide that but only to ensure that the sprint itself is not overloaded and thus an accurate estimate.

[–] ripcord@lemmy.world 1 points 1 day ago

(story points)

[–] criss_cross@lemmy.world 13 points 1 day ago (1 children)

Can you retell my company that?

[–] Kissaki@programming.dev 5 points 20 hours ago

For a small exorbitant consulting fee that legitimizes me, I can tell them that.