d(thoughts)/dt
Notes, opinions, and field reports — on AI-first workflows, web systems, backends, and the occasional bit of mathematics.
Go doesn't have classes, so how do you create objects? This post walks through structs, struct literals, zero values, value vs pointer semantics, and receiver functions — and why Go still isn't OOP.
Everyone is bolting a chatbot onto their product and calling it AI-first. The real shift is in how software gets built — and what it does to code review, testing, and taste.
Two years into React Server Components, the mental model finally clicked: it's not about performance, it's about deciding where data becomes UI. Notes from shipping a CMS on them.
I write both. The decision that actually matters isn't syntax or benchmarks — it's the failure model your service needs. A field guide from running JavaScript and Go in production.
I run both MongoDB and PostgreSQL in production. My default flipped years ago, and the reason isn't performance — it's that schemas are promises, and Postgres makes you keep them.
Everything I know about canvas performance came from a drawing app that stuttered. Frame budgets, pointer events, and the math-major habit that saved it — notes from building Slate.