> I love doing stuff that has long term stability written all over it I also love doing stuff that has long term stability written all over it. In my 20 year c

> I love doing stuff that has long term stability written all over it I also love doing stuff that has long term stability written all over it. In my 20 year career of trying to do that through various roles, I've learnt that it comes with a number of prerequisites: 1. Minimising & controlling your dependencies. Ensuring code you own is stable long term is an entirely different task to ensuring upstream code continues to be available & functional. Pinning only goes sofar when it comes to CVEs. 2. Start from scratch. The effort to bring an inherited codebase that was explicitly not written with longevity in mind into line with your own standards may seem like a fun challenge, but it becomes less fun at a certain scale. 3. Scale. If you're doing anything in (1) & (2) to any extent, keep it small. Absolutely none of the above is remotely applicable to a project like Ubuntu.