How I work
AI velocity.
Engineering discipline.
I’m an AI-first engineer. Coding agents write a large share of my first drafts, connected through MCP to the tools where real work lives. That’s the velocity. The discipline is what happens next: every architectural decision, every library choice, and every line that ships goes through twelve years of production judgment. Mine.
It also means the scope isn’t capped at one platform. Kotlin Multiplatform takes a single codebase to Android and iOS, and agentic AI extends the same engineer to the backend, the web app and the release pipeline around it.
Agents
- Claude Code
- Codex
- Gemini CLI
- Cursor
Connected to
- Jira
- Figma
- GitHub
- Firebase
The difference
Not a vibe coder. An engineer with a faster pen.
Vibe coding
- Accepts whatever the model outputs and moves on.
- Lets the AI pick libraries and patterns on the fly.
- Prompt, paste, pray. Architecture emerges by accident.
- Can’t explain the code when review gets hard.
How I work
- Reviews, corrects and re-architects the output with 12+ years of production judgment.
- I decide the stack and steer agents toward the right library — choices that stay future-proof, with fewer bugs and less repair work later.
- Architecture comes first. Agents implement to my spec — module boundaries, interfaces and state management are decided before generation starts.
- I own every line that ships — and can defend any of them in a code review.
The pipeline
Four steps, one owner.
01
Decide
Architecture, tech stack, module boundaries, interfaces. The decisions that make or break a codebase are made by me, before any code is generated.
02
Delegate
Coding agents — Claude Code, Codex, Gemini — implement to spec, connected through MCP to the real tools: Jira tickets, Figma designs, GitHub, Firebase.
03
Review
Line-by-line. I track what the agents used, correct wrong turns, and re-architect where needed. AI accelerates; it doesn’t get a vote.
04
Ship
Tests, CI/CD, store release, production monitoring. The same delivery discipline I’ve applied for 12 years — just reached a lot faster.
This isn’t theory. V-Assist — a production drone app — used AI tooling across its full development lifecycle. At Avetics I embedded Claude Code, Gemini CLI and Cursor into a 6-person team’s daily workflow. Football Predictor 2026 and Study Quran were shipped solo, at a pace that surprised everyone except the workflow. The results are on the projects page.
The reach
Past Android — without adding people.
Android is where my twelve years are. It is not where the delivery stops.
One codebase, both platforms
Kotlin Multiplatform puts the business logic, networking and data layer in one place and ships it to Android and iOS — with Compose Multiplatform sharing the UI where sharing it is the right call. I have shipped iOS features too, so I know where the shared line should fall.
One engineer, the whole product
Agentic AI extends my reach past mobile: backend, web, infrastructure and release automation, directed by someone who has shipped production systems for twelve years. For a founder or a small team that means an all-in-one software solution, not an app plus four more contractors.
Want this velocity pointed at your product?
Build your product →