Notes from the engineering team
What we have learned building and operating production systems — written for engineers, without the marketing layer.
Designing offline-first field applications that actually reconcile
Caching data on the device is the easy part. The hard part is deciding what happens when two people edited the same record in the same afternoon.
Read the articleEvaluating LLM features before you ship them
A demo that works on five examples tells you almost nothing. Here is the evaluation discipline we apply before an AI feature reaches production.
2 min read
Postgres patterns for multi-tenant enterprise platforms
Row-level security, partitioning and connection strategy — the three decisions that determine whether your multi-tenant platform survives its tenth customer.
1 min read
Threat modelling that a small engineering team will actually do
Formal methodologies stall in teams of six. A ninety-minute session with four questions catches most of what matters.
1 min read
Designing cloud architecture with the bill in mind
Cloud cost is an architectural property. Deciding it after deployment means paying for decisions you did not know you were making.
1 min read
Building CI/CD pipelines that teams actually trust
A pipeline people routinely override is worse than no pipeline. Speed and determinism are what earn the trust.
1 min read
Prefer these in your inbox?
We send one engineering note a month. No product announcements, no sales sequences.
Or email walter.mussagy@gmail.com — we reply within one business day.