this post was submitted on 14 Dec 2024

-3 points (20.0% liked)

Programming

18364 readers

194 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 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

-3

SAME STATS, DIFFERENT IMPROVEMENTS (cdn.masto.host)

submitted 2 months ago* (last edited 2 months ago) by LabPlot@floss.social to c/programming@programming.dev

1 comments fedilink hide all child comments

SAME STATS, DIFFERENT IMPROVEMENTS

After 12 months of managing #bugs, #developers A, B, and C changed their approach.

Assuming a steady flow of bugs of the same kind, whose change is an improvement❓

Boosts appreciated! 🙂 :boost_love:

More generally, the problem is domain independent.

#OpenSource #FreeSoftware #FOSS #FLOSS #Software #Tech #Development #Engineering #Business #Improvement #Software #Programming #Python #InfoSec #Statistics #Linux

top 1 comments

sorted by: hot top controversial new old

[–] deegeese@sopuli.xyz 2 points 2 months ago

A changed nothing, and I worry they’re managing to the metric.

B stopped opening and closing a large number of trivial bugs.

C did a cull of old bugs and changed their intake behavior but is growing a backlog.