Hacker News new | past | comments | ask | show | jobs | submit login

It shows ongoing impact rather than a one-time cost from an incompatible change.



For one team? at one org who didn’t keep their stuff up-to-date regarding one project.

A collection of tickets such as this one plus some analysis? Could be interesting. But this is just noise.

Edit: To be interesting, that analysis would have to compare with other kinds of breaking changes that happen in software constantly.


Or does the exception prove the rule?

The fact that this is the only instance of problems says that the change effectively caused no ongoing problems.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: