Home

Hot take: 200 characters is the sweet spot. Long enough for a real thought, short enough that you cannot hide a bad one behind filler.

New motion study: a like button that breathes. 320ms spring, 1.08 overshoot, particle burst on release. Full breakdown dropping tomorrow.

Orion 4.2 is live. Builds are 41% faster, the plugin protocol is stable, and there is finally a dark mode that respects your eyes. Changelog in the thread.

CSS tip nobody asked for: `text-wrap: balance` on headings, `pretty` on paragraphs. Two lines of CSS, instantly better typography everywhere.

Day 41 of building in public: 212 signups, 38 paying, $410 MRR. The whole product fits in 9 files. Constraints compound.

Docs are not a cost center. They are the onboarding funnel you forgot to measure.

Benchmark: 1M rows, 200 byte payloads, JSON vs binary. Binary wins on size, loses on debuggability. Pick your pain.

Poll: what should the reply box do when you cross the limit — lock the button, or keep typing and highlight the overflow?

Reminder that your database is not slow, your N+1 query is. I say this with love, from a person who wrote one this morning.

Gradient of the day: #1d9bf0 → #8b5cf6 → #ec4899. Three stops, 120 degrees, endlessly reusable. Steal it.

We removed 14,000 lines of code this quarter. The product got faster and the team got calmer. Deletion is a feature.

Accessibility win: every icon button in our app now has a visible focus ring and an aria-label. It took an afternoon. Do the afternoon.

Small thing that changed my week: a 200 character limit on standup updates. Everyone writes less, everyone reads more.

Wrote the release notes in exactly 200 characters and the support tickets dropped 18%. Brevity is a support tool.

Spent two hours optimising a function that runs once at boot. It now takes 40ms instead of 400ms. Worth it. Obviously.

Thread time: how we cut p99 latency from 840ms to 96ms in one sprint. Short version — we deleted a cache that was lying to us.