@spreadsheet_tabs
I model everything. Household cash flow, a side business, a fantasy scenario where I retire early. Half of it is genuinely useful.
The structural fix so it doesn't rebuild: separate the list of things you're doing from the list of things you might do. Two lists, hard boundary. The active one is allowed a maximum of around ten items and you're not permitted to add an eleventh without removing one. Everything else lives in someday, which you skim once a month and mostly delete from.
A list you flinch at is a list that has stopped distinguishing between commitments and ideas.
Also stop rebuilding the plan when it breaks. A wrecked Tuesday doesn't invalidate Thursday's blocks. The move is to drop today's remaining blocks and keep the rest of the week, not to declare the whole thing dead and freewheel until Sunday.
Worth knowing that hold lengths are often shorter for money you receive regularly. Banks build a picture of what's normal for your account, so a payroll deposit from the same source every month usually clears faster than a one-off cheque from someone you've never received money from before.
Forgetting a deliverable existed is the specific symptom I'd pay attention to. That's not laziness, it's that you're holding two sets of commitments in your head with no external system. Everything, from both jobs, goes into one private list that you own, reviewed every morning and every Friday. It won't fix the hours but it will stop the surprises.
One nuance so it doesn't get flattened the other way: the caricature of Buller was real and the underlying legal attitudes of the period were genuinely grim. What isn't supported is the phrase coming from any of it. Both things can be true and people tend to argue as though they can't.
Longer term, if tenants vary in size by three orders of magnitude, look at partitioning by tenant or at least keeping per-tenant statistics targets higher. The planner's default sampling is not great at very skewed distributions and you'll hit this shape of problem again on a different query.
Fair, though a form post and a table are about as legible as code gets. I'd worry more about handing over a bespoke state management setup.
It's phone photos and the occasional raw file from an old DSLR. So GPU it is.
Is buying a matched pair now not safer than adding a stick later?
That's not how it works. Current flows in proportion to what the device draws, and an idle switching supply with nothing attached draws a fraction of a watt. A meter on any socket will show you this in about ten seconds.
Your dad is describing a real effect at 1995 scale. A modern phone charger left in the wall with nothing attached draws something in the region of 0.1 to 0.3 watts. Twelve of those is a few watts, call it 30 kilowatt hours over a year, which is single figures in most currencies. It is not the reason your bill went up.
What is worth chasing, in rough order:
Buy a plug-in energy monitor for the price of a takeaway. Ten minutes of moving it around will tell you more about your specific flat than any amount of general advice, mine included.
There's your unplugging habit, and it's one plug rather than twelve. Turning off the rest mode in settings costs you a slightly slower start-up and nothing else.
And the rated life is usually the point where a big batch is down to 70% brightness, not the point where it stops working. Two different promises hiding in one number.
Two apps, and fix the gap instead of merging them, because the gap is a habit problem rather than a tooling one.
The rule that solved this for me: notes are allowed to contain tasks, but a task is not real until it exists in the task app. So when I close a meeting note, the last thing I do is copy any action out of it. Ten seconds. The note keeps the context, the task list stays the single place I look.
Merging into one tool usually produces a system where your task list is full of half-written paragraphs and you stop trusting it. The combined apps are genuinely good at one of the two jobs and mediocre at the other, and which one they're good at is easy to find out in a week of use.
On your actual constraint, browser access on a locked-down work laptop is the thing to test first, before anything else. Some corporate setups block the exact domains these tools use, and that's a much shorter list of candidates than the feature comparison suggests.
Always check that first. I once spent a fortnight setting up a system I couldn't open for eight hours a day.
Free tools that will get you a long way:
The metadata warning is not a small thing. Half the confident finds people post turn out to be a 1911 reprint catalogued as 1847.