Fable 5.1 is a lot better than Fable 5 btw (edit: in terms of writing style). Not sure about opus 5.5 yet since I’ve only got one session in so far.

I had a FitBit Charge 4 some years ago, but it stopped working after a couple years.

Then I got a RingConn 2 last year, but like TFA I've decided that I don't like the ring form factor.

Thanks for this great reminder that we can choose the kind of person we want to be.

How far does the HAL go? Screen 12 and 13, and writing directly to VRAM? WAIT for vsync? Call absolute for mouse usage?

Being in nature is good for us, so that’s probably part of it, as is the constant practice of being self-reliant.

Another theory is friction. I can’t just roll out of bed to the couch, and back. I don’t have a fixed place to shower, so I swim in a river most days, and usually it’s freezing. Camping alone was terrifying at first, but objectively not that dangerous and not worth worrying about. All these little moments are a chance to exercise that mental muscle to do uncomfortable things.

Modern life is devoid of this friction. I could try to take a cold shower every day, but a not-cold one is just a turn of the wrist away. I could try to make myself go outside a bit every day, but I don’t need to.

This isn’t a new observation, but I can’t believe how stark the contrast is. I’m getting stuff done that I’ve been procrastinating on for years.

The main reason we don’t use it anymore is that the default handlers don’t return the error type, which means error handling and HTTP status tracking get tricky and non-idiomatic as soon as your handlers start calling functions that can fail. It’s essentially a function coloring problem.

One could argue that HTTP status is a totally separate thing from normal errors, and I get that perspective, but that’s a significant ergonomic hit to take for the sake of philosophical purity.

The straw that broke the camel’s back was that Claude managed cloud agents are awkward to use with anything other than GitHub. In general, we realized that the whole world was on GitHub and we were swimming upstream.

But the original mistake was separating issue tracking and source control when we didn’t need all that power. Everything is so much simpler if you don’t have to maintain those integrations.

Maybe they’ll really enshittify GitHub in the future. We’ll cross that bridge when we come to it.

I literally maintain a conceptual-model.md that describes the “things” in our entire system, how they relate to each other, and some bits about how that maps to the code (the DB schema maps sort of closely to it but sometimes not that close, and so does the API, and that’s ok). I wrote most of the doc myself, but plan to coauthor with LLMs going forward.

So far it’s saved me tons of typing as I add features. I don’t have enough data yet on how well it will guide myself and others when adding stuff that really stretches the model, but I’m also optimistic that it’s a valuable approach.

Harder for brownfield projects of course (and it basically replaces Jira, which would cost me all my social capital if I try), so I won’t be adopting it now. But I will be leaning into long-lived organic, grass-fed assets like conceptual-model.md that‘s critical for evolving the product forward but doesn’t strictly map to the types in the code.

I really enjoyed engaging with the article. Loved the humor sprinkled in, and the humility demonstrated throughout. Some great first-principles clear thinking here.