Profile and Offer

Engagements

• Idea → production: your idea in the hands of real users in one to two months, built the way it will be maintained rather than as a demo to throw away.
• Architecture and foundations: the system drawn and the foundation stood up — framework and platform chosen, the structure and its conventions in place — for a team that will build the features itself.
• Your team on agent rails: the architecture, the staged pipeline and the pre-push gate that let a crowd of agents ship without drifting — set up on your codebase, then handed over as checked-in procedure rather than as advice. It has been handed over once already, and the engineers who took it carried it to projects of their own.
• Rescue and diagnosis: the prototype that got vibe-coded into a corner, and the agent that doesn't do what you expected — usually the same purchase.
• Standing technical judgment: build-vs-buy calls, and a straight answer on what the models still cannot do.

The Engineering System

• Feature-sliced architecture held by linters, so a crowd of agents working at once cannot drift the structure.
• A staged pipeline — plan, implement, review, finalize — each stage its own session, with reviewable artifacts between them.
• Branch hygiene held in-session: a gate of concurrent checks before every push, the production build among them, so no agent contaminates main with code that breaks it.
• CI/CD that fits your workflow — ship every commit off main, staging-based release cycles, or release trains.

AI Expertise

I tend to stick to a more "economical" paradigm of AI usage: smaller prompts, a close eye on context limits, and no hoping that a model fed everything will sort it out on its own. My expertise predates the ChatGPT hype cycle, which means I understand not just the APIs, but the patterns and limitations underneath them — which is where most of the hard problems live.

Working Style

Hands-on is the point: I set the direction and write the rules the work runs on, then stay in the code — reviewing what the agents ship, fixing what the gate catches, and deciding what gets built next. Give me the vector and I'll own the result as if the company were my own.

Handing over is part of the job rather than the end of it: the procedure lives in the repository, where the next engineer will find it, and at Playgram I mentored two developers along the way.