M contents/articles/convergence.md → contents/articles/convergence.md

@@ -28,7 +28,11 @@ The solution? Easy: [Sourcehut](https://sr.ht). I had been using it as a mirror for most of my projects for quite some time, but I was not ready to switch, mainly the possibility to create GitHub actions to cross-compile my programs so that I could distribute the binaries when I released a new version.
 
 Actually, Sourcehut has an awesome [build](https://builds.sr.ht)service for *nix systems, but it doesn't offer a way to build for macOS and Windows. And for sure I always wanted to ship the binaries for my software for those platforms as well, right? Well, meh...
 
-Truth is, I now have two kids and a full time job, I am the main user of my ecosystem of highly-opinionated tools and keeping all those actions running smoothly had become a second (or third) job.
+Truth is, I now have two kids and a full time job, I am the main user of my ecosystem of highly-opinionated tools and keeping all those actions running smoothly had become a second (or third) job. So I was like, you know what? No more binaries distributed for any release of my software! Ah, that felt really good, and gave me the final push to make the move official. 
+
+And it turns out, releases are overhyped. I was recently discussing with [Devine](https://wiki.xxiivv.com/site/devine_lu_linvega.html) about [Kelvin Versionjng](https://wiki.xxiivv.com/site/kelvin_versioning.html), and while I like the idea of software aiming at becoming more stable, I just didn't like the whole decreasing temperature thing, and the way dependencies are managed.
+
+But I like the concept of software _converging_ to ultimate stability, maturity, and dependability. Oh yes I did...
 
 ### Convergent Versioning