Voidloop helps me sleep
Voidloop on Steam is a simple incremental game for bed.
Stanning exe.dev
It's fast. It's fun. It's software prototyping, pet projects, and agent sandboxes rolled into one giant bouncy endorphin rollercoaster.
For personal reasons, I'm late to the persistent-agents-and-coding-from-phones party. My home server died, and I couldn't summon the motivation to scavenge for parts. I've worked from laptops ever since: no persistence, no remote Claude Code sessions, no blinking lights.
Anyway: exe.dev is the easiest way I've found to dip your toes into coding agents from your phone.
Communicating expertise
Tuhin Nair’s article frames a common conflict. A business reduces uncertainty: ship an experiment, learn from the market, choose the next bet. Senior developers manage complexity and stability: keep the system understandable, reliable, and tied to clear responsibility.
Answering a request with maintenance costs addresses the wrong loop. A better response offers a shorter, cheaper experiment that answers the business question without binding the result to the core system. This turns technical judgment into a path toward evidence.
Becoming a day person
Recently read: Herman’s “On becoming a day person”.
Herman’s account feels familiar. Poor bedtime and waking discipline made my sleep erratic; insomnia made the pattern hard to break.
My solution was to get a wife with stronger discipline and piggyback on her routine. Sleeping pills helped make bedtime firm and mornings dependable.
Solving the infinite tabs problem
If you're terminally online like me, your tabs multiply like rabbits during deer season.
Each tab is a deferred decision, part of a backlog that never clears. There will always be more claims on your attention than you can satisfy.
Generalize this to everything in life, and you rederive the task management and prioritization problem.
How many woodchucks would wood chuck if wood could chuck woodchucks?
Reveal spoiler
If wood could chuck woodchuckers, wood would chuck as many woodchuckers as wood could chuck. (this is a spoiler block test)Writing short docs well
Tom Bedor wrote how to write good short docs. Most of it lands. Key takeaways, with some riffing:
Optimize for short attention spans. Think in tiers: the 5-second glance (title and first line), the 5-minute skim (summary and headings). This means: clear titles — the most important line in any doc. A concise summary at the top covering what's in scope and what's not. Strong headings. Collapsible/tabbed sections where the format allows.
Learning cooking like you learned programming, part I
A good programmer is an engineer. Just as you can apply the skills of a scientist or a Bayesian to many domains, the skills of an engineer are broadly applicable to other creative works like writing, woodworking, cosplay, or in this case, cooking.
There's just one problem: I've never learned engineering formally, so I can't tell you what the principles are. All I can do is map the introductory concepts of cooking onto the introductory concepts of programming.
Getting to Hello World
Writing out a program that prints "Hello world" is a rite of passage for anyone learning how to code. This has a couple of purposes. The first is to give confidence. The second is to set up your build environment. The last is to give the basic understanding of syntax.
The same concepts translate to cooking. You want a small success that gives you confidence to do more complicated things. You want to check your build environment — pots, pans, seasoning, spices, ingredient storage, knife, chopping board. You want familiarity with some basic skills.
First
So, I've finally gotten around to starting a blog, and I’m not entirely sure why.
I'm telling myself it's to clarify my thoughts and build a writing habit. This is a lie, of course. It's a self-improvement fantasy that will last, optimistically, until my next deploy breaks. In reality, it’s just another checkmark on the trendy developer to-do list, nestled right between "complain about Javascript" and "praise Rust."