Hi, I'm Mike John.

You work directly with the person shipping your product—fewer handoffs, faster decisions, and one owner for quality. I still follow structured milestones and written updates; you just skip the layers between you and the build.

Yes, when scope is honest. I break work into milestones with visible deliverables, ship in small testable increments, and use a modern toolchain (TypeScript, automated checks, solid Git hygiene) so changes stay predictable. If trade-offs appear, we adjust the plan together instead of quietly slipping the date.

I treat AI as an accelerator, not a source of truth. I review every important change, keep secrets out of prompts, and default to secure patterns for validation, auth, and data handling. Linters, tests, and dependency review still apply—especially for anything touching money, PII, or auth.

Discovery and scope → UX/data-flow design → implementation in milestones → QA and performance → launch and handover. You get regular updates, a clear changelog, and preview builds when it helps so feedback stays concrete.

I build modern web apps with TypeScript, SvelteKit, Tailwind, and component-driven UI where it fits. I integrate REST or GraphQL APIs, databases, auth providers, and CI/CD, and I optimize for maintainability so the project is easy to extend or hand off.

I am comfortable with async communication (email, chat, Notion) and scheduled calls when we need to decide something together. I share repos, PRs, and preview deployments so you can review progress without waiting for a big reveal.

Often, yes. I start with a short review of the repo, deployment, and pain points, then propose incremental improvements. I will say no if the timeline or risk does not match what you need—I would rather be upfront than optimistic.

Yes. I can cover stabilization, fixes, and follow-on features, and I can document the system so your team—or another developer—can run with it. Ongoing work is usually scoped as a small retainer or milestone-based sprints, depending on what you prefer.

I work well with distributed clients: clear written updates, overlapping hours for reviews when needed, and async-friendly workflows so decisions do not get stuck waiting for a meeting.