Building software that makes complex things clearer.
Independent notes on engineering, systems, and product craft.
Featured writing How to Build Conversion Data Everyone Can Reproduce
Latest writing
-
01 When AI can approve a pull request
What AI pull request approval changes about governance, ownership, permissions, evidence, and safe software delivery.
15 min Read more -
02 What scaling an ASP.NET Core backend actually requires
Learn how to scale ASP.NET Core backends with explicit boundaries, caching, database discipline, timeouts, retries, and observable failure handling.
13 min Read more -
03 AI-assisted code analysis you can actually trust
Design AI-assisted code analysis with repository scope, evidence links, calibrated confidence, reproducible results, and human review.
13 min Read more -
04 Designing real-time analytics with ClickHouse
Design ClickHouse real-time analytics with event schemas, tenant scope, query performance, aggregation, freshness, and late-event handling.
13 min Read more
Field notes
- 001 principle
Latency budgets are design tools
The 200ms budget is not only an SRE metric; it shapes what the interface can promise and when it should ask the user to wait.
3 min - 002 principle
Naming is part of system design
A system is only as clear as its worst name. Renaming is refactoring, and the cost of postponing it compounds across every boundary.
3 min - 003 experiment
Streaming rows changed the way the table was read
Replacing pagination with streamed rows was not only a speed experiment; it changed how people scanned, paused, and trusted the data table.
4 min