Contact
If you’d like to get in touch with me, please email me:
How I can help
You can email me if you think I may be useful in one of these areas:
Architecture and technical direction
Designing systems, APIs, service boundaries, and long-term technical plans.
AI tooling for engineering teams
Introducing agentic coding and AI-assisted workflows into a team: tool selection, guardrails, and measuring what actually helps.
LLM and agentic tool evaluation
Choosing models and AI tools for a specific job — I benchmark them on my own project specs (Prompt Vault), not on vendor demos.
MVPs and product prototypes
Turning an idea into a working first version with a clear scope, pragmatic tech choices, and AI-assisted development where it genuinely speeds things up.
Backend, cloud, and full-stack development
Building practical web products, internal tools, APIs, and cloud-side systems.
Codebase review and modernization
Improving maintainability, structure, reliability, and developer experience.
macOS / iOS app development
Designing and building native apps for Apple platforms, from prototype to App Store release.
Open-source and independent projects
Questions, feedback, collaboration ideas, or discussions around my public projects.
What to include
- A short description of the topic or problem.
- Relevant links, screenshots, logs, or examples if they help explain the context.
- For app development: target platform, core idea, current stage, and release goals.
- For project-related messages: goals, rough timeline, and current state of the project.
Why email: Messaging apps and social networks are convenient for quick chats, but they often lack the structure needed for professional conversations. I prefer email because it remains reliable for correspondence, context, and long-term records.

