For me the yellow slice is others being stressed about me not being productive whilst I'm trying to sleep and get back some spoons(*) so I can function. Otherwise pretty accurate.
(*) https://en.m.wikipedia.org/wiki/Spoon_theory
Edit: PS. I tend to watch Machinist and Maker videos rather than cats, but that's just me.
Dat lijkt me een goed idee :)
No .. just more in focus..
Further down the article it talks about why it's that colour.
What's even more remarkable is that someone actually did that, in January 1998.
So .. hot air doesn't float .. that's a thesis right there.
So .. hot air doesn't float .. that's a thesis right there.
I understand.
I'm not trying to discredit your response, just pointing out that this is not a trivial problem to solve and any quick solutions are unlikely to make this easier for anyone involved.
For example, if you do burn a new DVD as suggested, you just created a versioning and distribution issue for yourself and your loved ones.
Before you start consolidating, consider what might happen if the switch is in an unexpected state. For example, someone turned off the heater or pump and you were expecting it to be on.
In other words, you need to consider what a "safe state" is for each thing and how your code, when it fails, reverts to that state. This is an example of "failsafe".
Note that I said "when it fails". This is true for all software, even on mission critical systems.
Source: I write software for a living.
Yes, this is an option. It requires that your password(s) don't change. Setting up a password store somewhere and granting access to it using this method is a potential solution, but not great.
When you discover something that's been missing in your life that you didn't know you needed.
Welcome to the club!