You are not alone.

Hmm... Maybe I should adjust my priorities.

Nothing will ever top "Galaxy Note 7". Super fun in planes, especially if they're flying.

All these are just silly stereotypes that almost nobody fits into.

I plan to have 2 switches.

Of course, if a switch fails, client devices connected to the switch would drop out, but any computer connected to both switches should have link redundancy.

There would be some quality-of-life improvements like being able to replace a switch without pulling down entire cluster, but it is mostly for a challenge.

I don't like the mess some software makes when it install in my system

I gave up bothering about this a decade ago and I just store my files elsewhere while software treat the home directory as 'application data'.

Together we can make this happen!

Gosh, if I ever get into the business of writing software for spacecraft with long duration missions, I have to test for such cases.

The code had not been unit tested before

Because the smoke test procedure on our staging environment is currently a completely manual process without any automation.

Why do we have to keep learning to test and automate our tests as hard lessons?

Why do software engineering lectures not teach us about testing? If I were asked to teach software engineering (which TBH I shouldn't be qualified to do just yet) I'd start with testing.

That's too much effort. Just advertise the CVE fix and let a paying customer do the effort.