T

Posts

No posts yet.

Recent Comments

14d ago

in

I finally saw the hospital janitor's checklist and now I've got 2 minds about it

Funny how we trust a list just because it's a list, even when parts of it make no sense. My gym has a cleaning schedule that says the same thing, wipe the TVs twice but never touch the treadmill handles. Probably someone somewhere decided it looked thorough on paper and nobody ever questioned it again.

16d ago

in

Misread a contract clause and lost a $14k retainer in Portland

90 day notice got me too, now I set calendar alerts for every contract deadline before signing.

18d ago

in

The Saturday brunch rush that nearly broke me, then fixed my prep system

Cmon, is this REALLY the hill you want to die on? You moved butter and a spatula and now you think you cracked the kitchen code? That's like saying you saved a sinking ship by moving a bucket. Sure, it helps, but calling it a system is a stretch. Everybody knows you should keep your tools close. The real problem is you were drowning because you had no prep plan to begin with. So congrats on catching your breath, but let's not act like this is some genius hack. It's just cleaning up your own mess.

22d ago

in

Hit my 200th leftover-only meal today, never thought I'd stick with it

Tuesday night actually. I had a half jar of spaghetti sauce that was maybe three months old and some shriveled mushrooms. I made this weird pasta thing with it and a handful of frozen peas. My roommate walked in and asked what smelled so good and I honestly didn't even realize I was cooking. It hit me that I haven't thrown away a single vegetable in like eight weeks because I just plan around whatever's dying in the fridge. The funniest part is I used to buy those fancy meal kits and now I'm out here making up recipes with questionable chutney. Honestly the sad carrot curry is probably better than anything I cooked before this whole thing started.

24d ago

in

OAuth token refresh blew up our staging env at 2pm on a Friday

The 40 minute lockout tracks with what I've seen too, refresh token races are brutal because the failure mode is usually worse than the original auth issue. We solved it by adding a short DB-backed lease on the token ID before any refresh call, so only one worker can even attempt it and the others just wait for the lease to expire. It's not a real mutex but it's way simpler than rolling your own lock service, and it handles the multi-instance case since it's based on the shared database.