Programming

17853 readers

435 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

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 [email protected]

founded 2 years ago

MODERATORS

[email protected]

-24

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

submitted 1 month ago* (last edited 1 month ago) by [email protected] to c/[email protected]

5 comments fedilink hide all child comments

SAME STATS, DIFFERENT IMPROVEMENTS

@programming

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

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 1 month ago (1 children)

@LabPlot @programming I'd say its difficult to tell without at formal statistical assessment, but if I had to pick, i'd say B. The difference between pre and post in A is just a continuation of a pre=existing trend. The difference in C looks like it might be reverting to mean over time, or even getting worse than it was prior to the change if the study went on longer.

[–] [email protected] 0 points 1 month ago

@IanSudbery @programming

Assuming a steady flow of bugs of the same kind, we share the same line of reasoning.