Knowing when and how to make breaking changes is tough. It is even tougher in the Go ecosystem. After being burned by making a breaking change and annoying people, I’m going to investigate how best to mitigate this annoyance. Disclaimer: This is mostly opinion, and only my opinion. This post is not associated with my employer in any way. You can contact me @normankev141 What even is a breaking change, anyway A simple definition of a breaking change is any change you make to your code that could break other code which directly or indirectly depends on it.
As a kid, I used to love playing Minecraft. I was technically precocious from a fairly young age, and naturally gravitated to attempting to host my own Minecraft server for me and my band of geeky pals to play on. The problem was, I had no idea what port forwarding was, nor how to log into a router. The solution I found was about as novel as it was dumb.
A long time ago I worked for an ISP as Tier 1 technical support. This is just one of many stories I have from my time here. These were originally published elsewhere on the internet, but are being reworked and republished here. Sometimes, the degree of insanity in a conversation can reach such a fever pitch that it is hard to recover. Sometimes, people can say things that leave you so flabbergasted that you aren’t sure if you’re being trolled or not.