213
AI Software Development – What Does The Data Say? (codemanship.wordpress.com)
submitted 3 weeks ago* (last edited 3 weeks ago) by to c/programming@programming.dev
67 comments fedilink hide all child comments
 

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
[–] 112 points 3 weeks ago (3 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.

  • permalink
  • fedilink
  • source
  • hideshow 6 child comments
    •
  • [–] 46 points 3 weeks ago (2 children)

    Has management known that?

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 9 points 3 weeks 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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 2 points 3 weeks ago

    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.

  • permalink
  • fedilink
  • source
  • parent