Dana

Sleeping nap is a fourth one, from Old English hnappian, to doze. So the score is four independent naps, which is a decent haul for one syllable.

Wallpaper. Sounds daft, works instantly. Solid dark blue on one, solid rust on the other, and set the browser and terminal themes to match. Peripheral vision catches colour before it catches window titles.

Also worth noticing that the sticky notes are working. That's not fraud, that's data. They work because there are six of them, they're visible without an action, and they get thrown away. Whatever you build next should have those three properties.

Two to three months for most people I've talked to. It never went fully quiet for me, but it dropped from a hum to something I notice maybe once a week.

One more that bites people once: Secure cookies require HTTPS, and if your staging environment terminates TLS at a load balancer and talks plain HTTP to the app, some frameworks decide the request is insecure and silently refuse to set the cookie. Look for a trust proxy setting.

Then over-deliver on it for the first month. Post before 9:00 every day, be specific, flag blockers early. After four weeks of that nobody remembers you're not on the call.

Ask one of them to let you go async, and ask for it as a working style thing rather than a scheduling thing. The phrasing that has worked for me three times: I get my best focused work done first thing, I'd like to post my update in the channel by 9:00 each day instead of attending, and I'll join live on Mondays and any day there's something to discuss.

Most managers say yes to that because a written update is genuinely more useful to them than watching someone recite it. Pick whichever team already communicates in writing a lot, that's the one where it'll land.

Longer term suggestion: reverse proxy the API onto the same origin as the frontend and CORS stops being part of your architecture. Every project I've moved to that setup has permanently deleted a category of bug from its life.

The bit people find genuinely surprising: a cheque can be returned unpaid weeks later in some systems, long after the funds became available. Availability is a promise about when you can spend it, not a guarantee that it's yours forever.

That's the normal outcome. The backlog is nearly always fear rather than value, and the ten day rule just makes the decision for you.

Processing is a separate habit from capturing, and it needs a scheduled slot the same way capture needed a trigger. Fifteen minutes at the end of each day beats two hours on Sunday, because the one-word notes are still decipherable on the day you wrote them.

When you process, every item gets exactly one of four outcomes and you're not allowed to leave it in the inbox:

• Do it now, if it's under two minutes
• Put it on the list with a next action that starts with a verb
• Put it in reference, if it's information rather than a task
• Delete it

Delete is the one people don't use enough. For the three week backlog, honestly, delete anything older than ten days without reading it carefully. If it mattered, it'll come back.

And internal tools live for years. The one that's still trivially runnable in 2029 is the boring one with no lockfile full of frontend dependencies.

Server rendered, and the deciding argument is not elegance, it's that you're one person with a deadline.

A SPA plus an API is two deployables, two error surfaces, a serialisation layer between them, an auth story that has to work in both, and a build step that will break on a Wednesday. For three screens and 40 internal users, every one of those costs are real and none of the benefits are.

The table filter and the form submission are both fine as normal form posts. If you want the filter to feel snappy, add one small library that swaps a fragment of HTML and you're done in an afternoon.

The other question I'd ask: which one makes you more employable in two years? A year of dull salaried work plus a year of contract work on interesting problems reads better on paper than two years of the dull thing. If the contract is genuinely teaching you something, that has a cash value even if it's hard to put on a spreadsheet.

Write yourself a checklist of the actual steps and follow it in the same order every week. Most of the two hours is probably deciding what to look at next and getting distracted on the way there. Mine is eleven lines on an index card and it's the reason it takes half an hour.