After two years increasingly complex web apps will have made your hardware obsolete. Batteries can be swapped, bad web development at scale cannot be fixed.

There's Paramiko, but Python is still a huge liability in memory-constrained systems.

If 250 W (in the absolute worst case, a 100 V .jp grid) is not enough for travel purposes, I have no idea what will satisfy your requirements.

The last time I felt the same was when I accidentally found a Japanese Youtube channel that had tons of clips of konbini storefronts, a few seconds long each, most of them with zero views.

An Nvidia employee once told me that one of the easiest ways to squeeze out a few extra frames on your old machine is to rename the game executable to hl2.exe.

[1] https://www.kobo.com/kobo-writing-life/blog/our-commitment-t...

Fail safe noisily and implement a cooldown period.

Another commenter suggested using LLMs, but I disagree. Having clangd emit warning squiggles for unchecked operations (like signed addition) would be a good start.

How many times have you reviewed your old code and been appalled at the terrible quality? You personally created slop; it's no different from GenAI output except that a human had to spend precious time crafting it. You likely were indeed bottlenecked by your ability to churn out code that you just had to get to work, for one reason or another.

The real issue is in the asymmetry when one party can use automation to create more code than another party can possibly manually verify.

I've already dealt with the fact that I will not get my mom back.