Take-Home Assignments That Don’t Waste People’s Time
I’ve been on both sides. The good ones share scope, time boxes, and a clear rubric.
All posts, sorted by most recent.
I’ve been on both sides. The good ones share scope, time boxes, and a clear rubric.
Flexbox for one axis, Grid for two — and the mental model that unblocked me.
I got tired of never publishing. So I wired WhatsApp → n8n → GitHub and made posting as easy as texting a friend.
The model doesn’t have my job stories, my bad deploys, or my taste. I use it anyway — just not the way the Twitter takes suggest.
n8n looks like a toy until you’re debugging a 2 a.m. webhook. Here’s how I use it for real work — including this blog’s publish pipeline.
Docs, source, and rubber duck — not virtue, just a forced reset.
Slack is loud. PagerDuty is serious. Email is the boring pipe that never left.
I’ve switched editors three times. The only thing that moved the needle was learning my debugger.
Versioning, pagination, and the boolean that meant three different things.
A repeatable order of operations: entrypoints, data flow, then opinions.
The stuff I verify before telling a client ‘it’s live’ — env vars, redirects, and the OG image that wasn’t.
One outage taught me why JSON logs and correlation IDs aren’t resume fluff.
How I knew it was dependency bloat, not ‘best practice,’ keeping it around.
Honest post-mortem: speed, DX, and the moment I missed dicts more than I expected.
None of these are flashy. That’s why they survived my laziness.
Spoiler: it wasn’t. A Postgres story about locks, bad timing, and the one checklist item I skipped.