@mathias Golden rule of a senior SW professional: _do not change the winning configuration_.
@FailForward what if updating makes me win more, things I do not know about yet, hidden gems of incredible functionality I had missed, and opening up to possibilities I can only dream about? What if something goes wrong when I am forced to update anyways? Should I not be ahead of the curve instead of being reactive? So many questions… 😆
@mathias
1. if it's a pure hobby, go ahead and have fun.
2. If it's a production system, do not mess with the nature. It's better to have a running COBOL machine with 0 downtime for 20 years, than a "modern &^%*@" which delivers only 75% of time and is a PITA otherwise.
3. If it's a thing in between, apply own judgment, for instance like this: "my past experience shows that now I am about to spend 4 hours of my time just to end up where I am already today. In those 4 hours, I could have gone for a walk with the love of my life, play a game of chess with my child, or read a book 🤔 ".... And then recall my golden rule again 😄 .
@FailForward As so often these days I missed the opportunity of “many free hours” and instead went for the second sleep, but yes, otherwise it is mostly a hobby thing: I like tinkering. I like fixing (computer-ish) things that I often have broken myself and then I need to sort them out. In this particular case it would be for the four VPS servers I have running in the cloud, of which this is one of them, but I can start in a completely “safe” area with a server I have yet to put to good use. Usually it isn’t those that break things though, simply because there isn’t much to break. 🤣