Auto-installing random software is the problem. It was a problem when our parents did it, why would it be a good idea for developers to do it?
Auto-installing random software is the problem. It was a problem when our parents did it, why would it be a good idea for developers to do it?
I run a distro that often causes software like this to break because their silent automatic installation typically makes assumptions about Linux systems which don’t apply to mine. However I fear for the many users of most typical distros (and other OS’ in general as it’s not just a Linux-only issue) who are subject to having all sorts of stuff foisted onto their system with little to no opportunity to easily decide what is being heaped upon them.
Ruby gems are older than that, but I have no idea what capabilities it has/had.
(Obviously some developers are better or worse than others, so I presume your observation is assuming developer skill as a constant.)
1) As org size grows, it's the team's average quality that matters (so yes, large numbers).
2) Even with a single team, the velocity will increase to match the acceptable level of quality.
Management will push the accelerator until they get too many bugs, then it will be "we need fewer outages".
So, in an team+environment, you end up with a constant (in time) detection rate, which basically means a constant in time injection rate.
If the teams' velocity increases without increasing quality, the bug injection rate (and detection rate) will increase.
AKA if the AI is slightly worse, but 10x faster, stop carrying the pager. :)
yolo!