Notes from a Principal Platform Engineer
I design software
platforms that make change
inexpensive.
I’m Antonio, a Principal Platform Engineer. I share the decisions and tradeoffs behind software that teams can confidently maintain and evolve.
From the field
Business capabilities should outlive vendors.
Lessons from designing a commerce platform around pricing, payments, loyalty, and fulfillment.
Read the case study
Principles
All design principlesOptimize for the next engineer
Make dependencies, ownership, and failure behavior easy to understand. The next engineer should be able to build on a decision without reverse-engineering it.
Prefer practical simplicity
Choose the least complex architecture the team can confidently operate. Add machinery when the business problem justifies the cost of owning it.
Recent writing
All writingAdapter Boundaries That Make Change Cheaper
How to design adapter boundaries that contain vendor semantics without hiding business-critical differences or creating a private framework.
One Model, Many Conversations: LLM Serving, Memory, and Reasoning
How serving engines share one model across users, isolate KV caches, batch token generation, preserve context, and spend more inference compute on reasoning.
From GGUF to GPU: How llama.cpp Actually Runs a Model
Trace llama_decode through GGML graphs, CUDA kernels, GPU memory, and next-token generation—and see why expensive LLM inference can still be fast.
Work with me
Bring the platform challenge.
I help teams review architecture, untangle enterprise integrations, and plan migrations without interrupting the business.