The blog
Long-form write-ups on AI engineering, mobile architecture and the plumbing that keeps teams shipping. No listicles.
The release went out, the feature went live, and the team moved on. Except “it launched” and “it works” are different claims — and the second one needs evidence. Here's the instrumentation stack we check before we call anything finished.
#Analytics#PostHog#Sentry#Observability
Read article
In a product company, new requests arrive every day. Launching each one at full scale is how you find out — publicly — that the flow is confusing and nobody understands the feature. So we built a flag system with six levels of “on.”
#FeatureFlags#ReleaseEngineering#Rollout#ProductEngineering
Read article
A support chat answers the moment someone asks, from saved FAQs and the page they are on. Slack is where you jump in, or edit those FAQs from the thread.
#RAG#LangChain#Slack#CustomerSupport
Read article
A customer asked to connect their own tools to our product. We had hundreds of working endpoints and nothing to hand them. This is the build log for the public API — including the incidents that taught us what to log.
#RESTAPI#APIDesign#Firebase#Nodejs
Read article
A user acts as themselves in the morning and as their organization in the afternoon. Supporting that is one parameter on every API call — if you design it in early. Bolting it on later touches every endpoint you own.
#Architecture#Identity#Multitenancy#APIDesign
Read article
A plugin is one React component, bundled to a single file and evaluated on our page — no iframe. The sandbox injects everything it may touch; the server believes nothing it says.
#React#Plugins#Sandbox#PlatformEngineering
Read article
AI coding agents sped up pull requests and made CI the slow part of the day. The pipeline now follows the diff, and that cut the time CI consumed by 45%.
#CICD#DevOps#AIDevelopment#pnpm
Read articleI take on a few projects at a time and am happy to compare notes before you commit to anything.