— Engineering notes
How we actually build the hard parts.
Deep dives into the systems we design, ship, and keep running in production.
Written by the senior engineers who actually built these systems — no filler, no generic advice. Client and product names stay under NDA; the numbers and trade-offs are real.
Follow new notes via RSS200+
Projects shipped
Proposals, Not Actions: The Control Plane Behind Autonomous Infrastructure Agents
An LLM agent that hallucinates a destructive change does it with total fluency and zero hesitation — and at fleet scale, that stops being an anecdote and becomes a rate. This is the control plane we built for a multi-tenant agentic infrastructure platform: deterministic policy gates, blast-radius scoring, DAG-scoped locking, decision provenance, and just-in-time credentials that give you the leverage of autonomous agents without their blast radius.
August 6, 2026 · 14 min read
Read articleHow much will an AI feature cost to run? A per-request cost model
The cost of an AI feature is the tokens you send at the input rate, plus the tokens the model writes at the output rate, times the calls one user action makes and how often users act. This guide works through that model step by step: what makes the bill grow, when prompt caching really lowers it, which model should do which job, three layers of caps, how to log cost from usage data, a worked example with illustrative numbers and what to do when prices change. Provider facts come from official pages read on November 16, 2026.
November 16, 2026 · 18 min read
Read articleNo-code or AI app builder, or a custom mobile app? A decision table
A no-code or AI app builder is the right answer for a prototype, an internal tool or a first test; a custom mobile app is the answer when the app is your product. This guide gives a decision table, then the criteria that decide it: how the app stores treat apps made by a service, whose developer account the app lives in, who owns the data, and what maintenance the first release creates. It ends with eight questions to ask before choosing a tool and a way to start light without locking yourself in.
November 16, 2026 · 17 min read
Read articleHow to write a software project brief: a template to fill in before you ask for quotes
A software project brief is the document you write before you ask anyone for a quote: the problem and who has it, how you will know it worked, what exists, what you do not yet know, your constraints and what you want back in the reply. The proposal and the scope of work are what the supplier writes in return. This guide gives the ten headings, weak-to-strong rewrites, the decisions a mobile app adds, the requirements people forget and a template to copy.
November 9, 2026 · 17 min read
Read articleWho can take over an unfinished software project? Five options, twelve questions and a scoring sheet
Who can take over an unfinished custom software project? The previous team, a new software company, an independent developer, your own hire, or a split in which one party assesses and another builds. Which fits depends on why the project stopped and what you must be able to prove afterwards. Secure the access first, keep the assessment separate from the work, and ask every software project rescue partner you consider the same twelve questions in writing. The guide adds a comparison table, a green-amber-red reading and a scoring sheet.
November 9, 2026 · 17 min read
Read articleShopify or custom e-commerce software? Seven thresholds you can measure on your own store
Whether to choose Shopify or custom e-commerce depends not on revenue or product count but on seven behaviors of your store: customer-specific pricing, quote and approval flow, multi-warehouse stock, ERP sync, payment country and methods, the total of transaction fees, and API rate limits. An off-the-shelf platform is enough if all seven pass. You test each threshold in a trial store against the platform's own documentation. The article gives the seven tests, a red-yellow-green reading and a copy-ready worksheet.
November 6, 2026 · 20 min read
Read articleAI agent or fixed workflow? Three architectures, four questions and an agent design card
Many jobs do not need an AI agent: use a fixed workflow if the steps can be written in advance, and a single call if one call is enough. An agent loop makes sense only where you cannot know the steps ahead, mistakes are reversible and you can measure accuracy. Four questions settle the AI agent or workflow decision, and every limit on an agent's authority belongs in a gate outside the model. You also get permission design and a copy-ready agent design card.
November 6, 2026 · 19 min read
Read articleWeb app vs mobile app vs PWA: a decision matrix by device capability
Web app vs mobile app comes down to three questions: how often users open it, which device feature is needed, and whether offline work and a store presence are required. In our engineering judgment, a web app that works well on a phone is enough for most business apps; a PWA is its installable form, with limits of its own on iPhone. Device features or store distribution can tip it to mobile; if the answer is web, we will say so. A matrix and a device test sheet follow.
November 6, 2026 · 22 min read
Read articleLegacy software modernization: rewrite or replace step by step? A seven-question test
In legacy software modernization, "rewrite or replace piece by piece?" has no single right answer: incremental migration is needless overhead for a small, simple system and usually the safer path for a large one that keeps changing. This article tests the direction with seven questions: intercepting requests, code access, size, shutdown speed, natural boundaries, proof of today's behavior and a changing business. Then come the first slice, data, cutover and rollback, and a copy-ready slice plan. General information; scope is settled in a written quote.
November 6, 2026 · 22 min read
Read articleWhen n8n or Zapier is not enough: ten thresholds and failure tests before you build custom automation
For business process automation, n8n or Zapier is usually enough; if a broken flow costs little, staying with the tool is the right call. This article shows where that stops being true with ten thresholds and ten failure tests: duplicate events, concurrent events, a flow that stops halfway, who learns of a failure, versions and rollback, credential ownership, rate limits, retention, readability and exit. Each test rests on the tool's own documentation and runs on your own flow.
November 2, 2026 · 20 min read
Read articleDedicated team vs project-based outsourcing: eight criteria to decide
Software outsourcing is a choice between buying capacity and buying an outcome, and a separate question is who manages the work. A dedicated team suits continuously evolving product work where you hold the technical management; a fixed-scope project suits work whose scope can be written. The two are not mutually exclusive. This article compares an own team, a freelancer, a dedicated team and a fixed-scope project on eight criteria, with a decision worksheet and twelve questions to put to a supplier.
November 2, 2026 · 18 min read
Read articleOff-the-shelf or custom software? A total cost of ownership worksheet
The off-the-shelf or custom decision should be asked not as "which is cheaper?" but as "which has the lower total cost over my time horizon and at my scale?" This article splits total cost of ownership into eight layers, from setup and build to risk and exit, and gives you an empty worksheet to fill in from your own documents. There are no amounts in it; your quotes and price pages supply those. If an off-the-shelf product does the job, that is the right answer.
November 2, 2026 · 20 min read
Read articleHow to integrate AI into a product: a 14-point production checklist
How to integrate AI into a product comes down to closing the gap between a demo and production; choosing a model is the small part. This article lists 14 checks to run before launch: quality measurement, prompt injection, permissions, action limits, data flow, cost and provider lock-in. Each gives you how to test it, a pass criterion and a relative cost to fix, and a copyable evaluation set template is included.
November 2, 2026 · 21 min read
Read articleMobile app development cost: a line-item model and a quote comparison template
Mobile app development cost is not one number but a list of line items; its share is set by the number of screens and states, the back end and admin panel, features, integrations, platform choice and maintenance. This article gives no price figures. It offers a ten-line cost model, the ongoing costs of store accounts and requirements with official sources, and a template that compares three quotes on the same scope. A difference between quotes can often come from a difference in scope.
October 29, 2026 · 17 min read
Read articleHow to take over an unfinished software project: a step-by-step audit plan
How do you take over an unfinished software project? First secure what can disappear: access to the repository, hosting, domain, database and third-party accounts. Then follow a step-by-step audit: a clean-machine install, a restore from backup, security and data health, and a feature inventory. The decision to continue, partly rewrite or start over comes from a seven-dimension matrix and is written down with its reasons. Who should do the work is a separate question, covered in our guide to choosing who takes over.
October 29, 2026 · 18 min read
Read articleHow to read a software proposal: 12 red flags and a copy-ready SOW template
Read a software proposal starting from the scope, not the price: look for what is out of scope, the acceptance criteria, which delivery each payment depends on, and who owns the accounts and the code. Any line whose answer is not in writing may be a cost left outside the proposal. This article gives a ten-section proposal skeleton, 12 red flags, comparison tables, an example in which a one-line proposal becomes a scope document, and a copy-ready 12-heading scope of work (SOW) template. It is not legal advice.
October 29, 2026 · 19 min read
Read articleIs your vibe-coded app production-ready? A 15-point audit
A working prototype is not a production-ready app. Before you open an app written with AI tools to real users, audit the risks across fifteen items: secrets, authentication, authorization, input validation, the database, backups and restore, environments, error monitoring, dependencies, tests, performance, payments, personal data, cost and ownership. If any item on secrets, identity, access control, input validation, backups, payments or personal data has failed, do not go live. This article shows how to check each item and what counts as a pass.
October 27, 2026 · 24 min read
Read articleDesigning for the Link You Don't Have: Offline-First Coordination for an Autonomous Survey Fleet
A fleet operator's aircraft spend roughly a third of every sortie with no usable link to the ground — and the events that must never be lost happen inside that window. Here is the CRDT and delay-tolerant networking architecture we built so degraded connectivity costs fidelity, never safety data.
July 21, 2026 · 13 min read
Read articleA Price That Goes Backwards Is a Liability: Building a Sub-80ms Market-Data Fan-Out in Nineteen Days
A boutique derivatives desk needed live prices on thousands of trader terminals in under 80ms — and needed those prices to never flicker backwards, even under load. This is the sequencing discipline, backpressure design, and tail-latency instrumentation it took to deliver both, inside a four-week engineering window.
June 9, 2026 · 12 min read
Read articleNobody Is Coming: 41,000 Custom Energy Endpoints, From Bare PCB to Real-Time Analytics
A utility needed settlement-grade 15-minute energy data from 41,000 circuits bolted inside energized switchgear, on an eight-year battery, with no realistic possibility of a return visit. Off-the-shelf modems failed on both physics and economics, so we designed the hardware — and everything above it — ourselves.
May 14, 2026 · 19 min read
Read article— Have something similar?
The thinking here ends up in production.
Every post above traces back to a real decision on a real client project. If you're facing something similar, let's talk it through.