Writing
React interfaces, Node.js and Python APIs, CRM data models, and AI-assisted development. Each note includes an illustrative example and a related project.
Subscribe via RSSCards follow an assigned editorial timeline. Publication dates appear in each article.
Architecture · 5 min read
A prediction about AI application APIs: durable operation status and explicit recovery actions will matter as much as the initial submit response.
Editorial date
Architecture · 5 min read
Choose a progress transport around how quickly users need updates, while keeping a recoverable import status behind either option.
Editorial date
Architecture · 5 min read
Separate durable job state, temporary ownership, and accepted output so interrupted parsing can recover without stale workers overwriting results.
Editorial date
Architecture · 5 min read
Plan database changes around overlapping application versions, resumable backfills, and the point where rollback stops being simple.
Editorial date
Architecture · 5 min read
A repeated request and two competing reservations are different problems. Model their identities separately before choosing a constraint.
Editorial date
Architecture · 5 min read
Separate equipment identity from its floor-plan, rack, and signal-diagram placements so edits and engineering documents stay coherent.
Editorial date
Architecture · 4 min read
Choose configured mapping, LLM interpretation, or a combined route by examining the actual uncertainty in each vendor file.
Editorial date
Architecture · 5 min read
Use Ryan Dahl’s documented reflection on Node.js as a prompt for testing old assumptions, without turning reflection into a rewrite mandate.
Editorial date
Architecture · 5 min read
Use explicit ownership and small module interfaces first. Split deployment when an observed constraint justifies the network boundary.
Editorial date
Architecture · 6 min read
Design a React and Node.js SaaS application with clear boundaries for UI state, business rules, database access, and background work.
Editorial date
Architecture · 1 min read
Agree on the contract before anyone writes a line of implementation. Frontend and backend then move in parallel.
Editorial date
Architecture · 6 min read
In-memory, distributed, and HTTP caching each solve a different problem. Layer them deliberately.
Editorial date
Architecture · 2 min read
Shared code and atomic changes are great — until your build graph and CI become the bottleneck.
Editorial date