Jo Whitcombe

One practical thing nobody mentions: keep a text file of every bug that took you more than an hour, one line for the symptom and one for the cause. Mine is 190 lines after two years and I reread it before interviews. It is also the fastest cure for the feeling that you are not learning anything.

Infinite canvas is the one thing paper genuinely cannot do and it matters a lot for diagrams. Otherwise, agreed with you.

Fair, and the reverse is also true: the year my boiler and my roof went in the same six months, the thing I envied about renting was the phone call.

The three-hour diagram lecture is exactly where handwriting wins and I wouldn't fight it. What I'd add: record the audio alongside the ink, if your course permits it. Apps that link the audio timeline to the strokes, so you can tap a scribble and hear what was being said at that exact moment, are the single most useful study feature I have ever used and it saved me repeatedly when my notes made no sense a month later.

If it's going to nag at you long term, stainless-mesh and glass-bowl units do exist. I switched to a stainless basket model and honestly the food is identical and the cleaning is worse. It fixed my anxiety, not my dinner, and I'm at peace with that trade.

Ringing the switchboard genuinely works and I was terrified of it for a month. The script is nine words: hi, who looks after the production scheduling side there. They tell you a name, you say thanks, you hang up. No pitch, no attempt to get transferred. I did thirty in an afternoon and got twenty two names. Then the email is addressed to a person and mentions nothing about how I got their name.

The survivorship point is fair and worth repeating. Anyone reading this in month two: the distribution has a long tail and you are reading the tail.

Both kinds coexist forever anyway. I looked up the difference between two array methods this morning and I get paid for this.

Timer for starting only, ignore it for stopping. I have been treating it as a contract in both directions.

'Solutions to problems you haven't had yet' is going to sit with me for a while.

Heavy empty is the thing I was afraid of. Roughly how bad, next to a normal 30L?

Pick a project you actually want to exist, not a tutorial project. My third to do list app taught me nothing. A scruffy tool that tracked my bouldering sessions taught me forms, storage, dates and deployment because I kept wanting one more thing from it.

It is also why the middle is the worst place to be. Priced too low to justify sales, too high for impulse buying.

Which is most of why Cramer's rule is a nice fact and a bad algorithm. Fine for 2x2 by hand, useless past that.

This is the actual answer to the entire genre of question, and it doesn't get upvoted because it isn't an app name.

One practical thing: the price of these annual plans varies by region and by whether you've cancelled. Before you renew at full price, cancel and wait a week. I have never not been offered a discount.

Find out the exact render system and whether the installer is still trading. If it is a proprietary system with one approved applicator locally, that is your answer.

Set the target where you actually land and the whole day changes emotionally. Then push the edges from a position of hitting it.

Sequencing on that basis is the actual win: hardest category first thing, feedback heavy work after lunch, admin at the end.

Three to four hours is the number that keeps turning up, both in the deliberate practice research people quote and in every honest time log I have ever seen. Two is not a personal failure, it is the low end of normal for genuinely hard cognitive work, and six sustained across months is something almost nobody does no matter what their productivity newsletter says. The trap in your setup is that the calendar block is six hours, so every day reads as a sixty percent failure even on a good day. Block three, protect them viciously, and let the afternoon be admin without pretending otherwise, and you will probably get more done because you stop spending the last two hours feeling behind.

Slight counterpoint to everyone: fix the electric first. If your current grinder cannot go fine enough it is often because the burrs need cleaning or the adjustment travel is limited by a stop that can be removed. Worth twenty minutes with a screwdriver before you spend two hundred dollars.

Pin the old runtime, capture fixtures, then extract the 900 lines into a current template. Two weekends is plenty for that and not enough for a full repair.

The mental model that made this stop biting me: variables in Python are labels tied to objects, not boxes holding values. a = b sticks a second label on one object. Everything about mutable default arguments, aliasing bugs and this exact problem falls out of that single sentence.

I would not disable it. Chase the actual cause, which in your description is almost certainly the hub - devices coming back in a different order after sleep is exactly the symptom. Plug the mic straight into the machine, leave the webcam on the hub, and you keep a spare mic for the day your good one dies mid-call, which happens.

Eleven months, but I am being honest that I had an unfair advantage: my employer had an internal transfer scheme and I was already the person who fixed the spreadsheets. Going outside cold at twelve hours a week is a different race. If your current company has anything resembling a data or ops team, that door is far shorter than the front one.