- Your brand is expressed through the decisions you make: what you ship, who you hire, and what you improve even when nobody asks. Saying you care about quality means little unless it changes those decisions. Copying a bigger company’s appearance can also hide what makes yours interesting. Be clear about the problem you solve and let the product, website, and writing reflect the same beliefs. karrisaarinen.com/posts/brand-is-who-you-are
- Speed comes from good designs that scale well. PlanetScale’s Postgres router keeps query results in their original byte format and only decodes values when it needs them. For sorting, that means reading the sort keys while leaving everything else untouched. That architectural choice removes work from every query that can use it. Spending more time upfront on these decisions makes it easier to add capabilities while keeping the system fast as it grows. planetscale.com/blog/designing-neki-for-performance
- Making collaboration feel natural requires modelling what people expect in small details. If someone splits a paragraph while another person edits its last word, the edit should follow the text into the new paragraph. Typing after bold text should extend the formatting, while typing after a link generally shouldn’t. Stable text identities and explicit merging rules make these behaviours possible, including when people reconnect after editing offline. notion.com/blog/how-notion-handles-concurrent-editing-with-crdts
- Long-running agents need to know what happened before they crashed. Saving the conversation alone isn’t enough; you need to preserve progress, pending work, and which actions are safe to repeat. A search can usually be retried, but an interrupted deployment needs checking before running again. Making those distinctions explicit is what lets an agent recover without blindly repeating potentially consequential actions. earendil.com/posts/pi-durable
- Test your documentation by watching someone follow it without your help. Knowing your own software makes it easy to miss the steps and assumptions you’ve left out. Paying users about €150 for these sessions exposed broken links, confusing file instructions, unexplained terminology, and even a missing explanation of what the software did. Fixing the instructions between sessions lets the next person test whether they actually became clearer. shkspr.mobi/blog/2026/10/i-paid-people-to-try-and-follow-my-readme
What I’ve been reading (W42, 2026)
Brand through decisions, performance by design, collaborative editing, agents that recover, and testing documentation