If you switch to Scheme (or the few other tail-recursive languages), you can always use recursion, and it's the most efficient solution. It's a bit of a weird shift at first, and the hand-holding do, dotimes, loop macros will let you transition at your own pace, but soon all your "loops" will just be named-let recursion.
Rice cooker, after it's halfway, throw in an egg or two, leftover meat, can of beans, soup, or chili, whatever's available. It's nourishing and always tastes good.
iPhones have like 8-20 hours of charge now, depending on what I'm doing. My old iPod is <4 hours, maybe <2, but it's enough for a walk. And if I'm out, where would I be charging it? I don't usually carry a phone charger and wall wart. If I was out for days, I'd use my laptop to charge it, while listening ON THE LAPTOP, which has analog headphone jacks.
I have a lightning-analog dongle on my phone headphones, that works fine. I have another analog headphones on my iPod classic for walks. The terrible catastrophe of taking out the headphone jack is nothing. There's no situation where I'd be listening to my phone and want to charge it, if it's on the charger I have a computer with speakers.
I have a lot of lucid dreams, and they're often in a specific city, and sometimes I even go to work in these dreams. I haven't lived in a city and worked in an office in over 10 years, so it's some kind of reverse escapism. I can always leave, and weird stuff happens anyway. I wouldn't trust any of my work output there.
But to let a company try to take over your dreams and never let you escape, you need to stand up and fight that shit. Put them in a never-ending nightmare where nobody gives them money.
Perforce is great for dealing with media files, artists can actually use it without producing 500 variants of -new-old-2022-final-dontuse-revised-1.1-2023 filenames (I AM NOT JOKING.), and it doesn't slow down with a lot of media like git does (which has to check out the entire history). Since usually only one artist touches a file at a time, locking doesn't slow them down.
Subversion's kind of the same for devs. There's a single source of truth, merging and branching is a lot easier, but it's less possessive about files. You can do media in it, better than git, but not as nicely as p4. I have seen the -new-old filenames end up in svn, but if you delete a file and commit, it goes away.
"My project" doesn't exist in any team. It's everyone's project. A manager needs to have a long conversation with Pink Pants.
If you build your project at anything but highest error level, clang -Wall etc., you're letting errors in, relying at best on coincidence to work the way you think it does.
I get more than half the spaces, all the negative ones, but can't quite make a bingo without the center, which is the kind of pro-giving a shit about git nonsense I'd never utter.
Well now I just want to watch young people try to beat the unbeatable games of my yout'.
Prince of Persia, Mega Man X, Ghosts & Goblins, Ecco the Dolphin (my favorite, but I screamed so much at Ecco dying one pixel away from air). Zork without a walkthru. Solve all the puzzles yourself or by talking to friends also playing it blind.
And you paid $60 ($200 in today's bullshit money) for this, you can't get another for 3 months.
Actual soap, Lever 2000 boring odor, a bar lasts quite a while even with hard scrubbing. Shower gel is weird and wasteful, you have water right there in the shower.
I have some deodorant thing but it's unscented, just for the antiperspirant.
The low-gravity planets/moons we have access to have rather harsh radiation environments, too, so neither. Dig into the ground. You would put a bunker or dome up on the surface for observations and airlocks, but it'd be foolish to live that exposed on a surface without a deep well of atmosphere & Van Allen belts.
If you switch to Scheme (or the few other tail-recursive languages), you can always use recursion, and it's the most efficient solution. It's a bit of a weird shift at first, and the hand-holding do, dotimes, loop macros will let you transition at your own pace, but soon all your "loops" will just be named-let recursion.