Models inside the workflow
I integrate models from different providers via API into internal tools the team opens every day.
Limit: if the task doesn’t repeat, it doesn’t justify a model.
Since 2011 I’ve been fixing and modernizing systems businesses run on. Now with models, agents, and MCP servers in the mix, and a review of the code they produce before it ships.
Main tools: Java · Spring Boot · .NET · Node · Python · PostgreSQL · REST APIs · models · agents · MCP
Java 8 and JSP apps, old .NET, modules only one person understands. I read, I document, and only then do I change anything.
Copilots writing code nobody reads, prompts with customer data, agents with more permissions than they need. I review what goes in, what comes out, and what gets logged.
Reports that take minutes on huge tables. I measure, split, index, and measure again.
No CI/CD, no rollback, no staging environment. I build the path so a deploy stops being an event.
Third-party APIs, the same data in three databases, manual integrations. I define the contract and write it down.
Everyone deploys differently and nobody reviews code. I set up reviews, branching, and rules the team can keep.
I integrate models from different providers via API into internal tools the team opens every day.
Limit: if the task doesn’t repeat, it doesn’t justify a model.
Clear permissions, defined scope, and a log of what they do.
Risk: an agent without limits is an incident waiting its turn.
I connect models to in-house tools and data using MCP (Model Context Protocol), with the minimum access the task needs.
Limit: what the agent can’t read, it can’t leak.
I read what the model writes before it ships: input validation, contracts, error handling, dependencies, and tests.
Risk: fast isn’t the same as correct.
A model won’t fix a missing index, a badly designed data model, or a process nobody defined.
Limit: when the answer is code and not AI, I say so.
I don’t touch a line until I know what the system does and who uses it.
One thing at a time, with tests where possible. If the code came from a model, someone read it before it merged.
Documented code, recorded decisions, and someone on the team who understands what I did.
Stack: Java 8 · JSP · REST APIs
Stack: Spring Boot · React · PostgreSQL
Stack: .NET · Angular · SQL Server · Azure
CSP, self-hosted fonts, zero dependencies, and what a static site can’t protect.
Read
Why a missing index isn’t fixed with a prompt, and what to ask before integrating a model.
Read
The short list I use before approving a change a model wrote.
Read
Tell me what broke. There’s a person on the other side, not a bot.