Field Notes
Perspectives on AI-augmented software delivery, concise engineering write-ups, and honest comparisons, from the team building custom internal software every week.
BYOA: Bring Your Own App, and Keep the Work Without Keeping the Risk
Your teams have already built the tools. BYOA is the process we use to take those apps into jig, give them a standard auth, security, and governance layer, and support them like anything else we build.
Latest posts
6 articlesFive Signs Your Vibe-Coded Tools Are Going Wrong, and What to Do Before They Do
Adoption is nearly universal and the failure modes are now well documented. Here is how to tell which of your internal tools are already at risk, and the specific steps that reduce each risk.
The True Cost of Vibe-Coded Internal Tools: Five Cost Vectors vs. What You Budgeted For
Token spend is the cost every team measures because it arrives as a bill. Hosting, maintenance, lost institutional knowledge, and the cost of switching back all land later, on different budgets, and rarely get traced back to the tool that caused them.
SaaS, Agencies, and Software Factories: Which Risk Each Model Takes Off Your Desk
Four ways to get internal software built, compared on cost structure, ownership, and the price of a change: none of them removes risk, and each relocates it somewhere different.
The Software Factory Has Been Rebuilt Three Times. The Failure Mode Has Not Changed.
A 57-year-old idea now runs on autonomous agents: each time the software factory returns, the throughput gains are real and the cost lands somewhere the throughput numbers do not show.
Dev Agencies and jig: Which Fits the Job
Both build real software, and plenty of clients use both. They suit different shapes of problem, and the question worth asking is not which is better.
One email, every few weeks.
Delivery notes, comparisons, and the occasional argument with conventional wisdom. No sales sequence attached.