Technical writing

Engineeringnotesfromclientdelivery.

Short articles on architecture choices, operational trade-offs, and delivery practice. Written for technical readers, not marketing.

Featured
Architecture11 min read

Event sourcing: a pre-adoption checklist for long-lived systems

Event sourcing fits a narrow set of problems. This is the checklist we use before recommending it, based on ledger and analytics programmes we have operated in production.

Shigefumi
CTO · March 18, 2026
#event-sourcing#cqrs
Featured
AI and agents9 min read

LLM agents in production: failure modes the demos skip

Moving from a polished demo to tens of thousands of weekly customer touches requires explicit work on routing, tools, evaluation, cost, privacy logging, and escalation. Here is how we structure that work.

SoftFlex
Engineering · February 24, 2026
#llm#agents
Delivery6 min read

Weekly demos as an engineering control, not a status meeting

A fixed weekly demo with working software reduces the cost of catching misaligned priorities and hidden coupling before they harden in the codebase.

Rahul
Co-founder · February 10, 2026
#delivery#cadence
Architecture8 min read

PostgreSQL as default: when we accept a different primary store

PostgreSQL remains our default OLTP choice because it reduces the number of early decisions a team must make. We document the narrow cases where another engine is justified.

Shigefumi
CTO · January 22, 2026
#postgres#databases
Infrastructure7 min read

Minimal Kubernetes layout we reuse across most clusters

A small, boring, well-documented baseline is easier to hand over than a bespoke cluster layout that only the author fully understands.

SoftFlex
Engineering · December 15, 2025
#kubernetes#infrastructure
Product10 min read

One-day scoping workshop: boundary, flows, and first measurable outcome

A single agreed page of scope, written with stakeholders in the room, reduces downstream rework more than most tooling investments.

Rahul
Co-founder · November 2, 2025
#discovery#scoping