Breaking Changes Risks

Commenters debate the dangers of software changes, rollbacks, and reversions causing breakage, cascade effects, reliability issues, and difficulties in undoing decisions.

➡️ Stable 0.6x DevOps & Infrastructure
2,673
Comments
20
Years Active
5
Top Authors
#7233
Topic ID

Activity Over Time

2007
3
2008
10
2009
33
2010
38
2011
50
2012
47
2013
86
2014
112
2015
93
2016
134
2017
106
2018
168
2019
171
2020
221
2021
256
2022
262
2023
288
2024
278
2025
298
2026
19

Keywords

SEND LOT THE TIME WHOLE THEY CONTEXT EVERY YOLO API change purity break changes original conflicts remove compromised species sync

Sample Comments

jeffbee May 1, 2021 View on HN

That would break so many things.

rdl Apr 30, 2014 View on HN

Just rolling back changes to previous versions might be enough to cause problems.

ffrryuu Oct 25, 2013 View on HN

Well, they keep on reverting everything...

bilalel Jul 24, 2014 View on HN

I think this mistake had a cascade effect on the other ones. If you remove this one, a lot of other ones should be manageable.

azornathogron Mar 25, 2021 View on HN

I think you might inadvertently create a few new problems if you did this.

ncmncm Jun 29, 2022 View on HN

Reversing it at that point would make things radically worse.

bad_alloc Jul 5, 2023 View on HN

Probably something that works for them now and a change might degrade reliability.

spicyj Feb 19, 2014 View on HN

I'd assume that they've added a check for that now, but it's hard to predict beforehand what things will break.

DougBTX Dec 22, 2024 View on HN

Maybe the opposite, slow rollbacks cause escalating incidents.

dmix Oct 7, 2019 View on HN

Do you have any specific examples of what would break because of this?