Decisions — the record
04 notes · 4 domains
Selected
architecture
decisions.
If nobody writes a decision down, the same argument happens again in six months, usually with someone who was not there the first time. These are the short version: what the situation was, what constrained it, what I chose, and what it cost.
Where I did not record the alternatives at the time, the note says so instead of inventing a list after the fact.
2026 Budgeting latency across a local STT → LLM → TTS pipeline Measuring each stage separately showed transcription was the bottleneck, not the language model — 1.24s to transcribe 2.1s of speech, against 1.08s to generate the reply. AI systems
2024 Matrix as the messaging substrate for clinical communications Clinical messaging needs records that outlast the shift, data that stays on the customer's own servers, and a way for organisations to talk to each other. Matrix covers all three. Realtime systems
2022—2024 Treating chain integration as reconciliation, not as an RPC call The chain is the source of truth, its data arrives late, and it can change after we have already shown it. That makes this a synchronisation problem, not a client-library problem. Distributed systems
2018 Offline-first as the premise, not as a degraded mode Disaster software gets used hardest when the infrastructure is worst. If offline is only a fallback, the app is unavailable exactly when the data matters most. Mobile & edge
The systems these came out of are on the work pages.