Not every question fits a class.
You may be designing an AI product and unsure how the pieces should fit together. You may have code or architecture that needs another pair of eyes. You may want to understand a technical idea properly rather than collect another shortcut. Or you may simply have a problem involving technology that you have not yet found the right way to frame.
1:1 Studio is dedicated time to work through that problem together.
There is no fixed syllabus. We start from what is in front of us and bring in AI, software engineering, computational thinking, product thinking, data, design or other disciplines where they are useful.
For larger problems, we can decide after the first session whether continuing would be useful.
Models, agents, RAG, evaluation, APIs, workflows, system architecture, product feasibility, and deciding where AI is — or is not — the right tool.
Backend architecture, APIs, databases, deployment, debugging, technical trade-offs and turning an idea into something buildable.
Breaking down complex problems, identifying rules and constraints, modelling processes, reasoning through edge cases, and deciding what should be automated.
Questions that sit between technology, product, business, design or data — where the difficulty often comes from the connections between them rather than any single field.
A class begins with a syllabus. A 1:1 Studio session begins with your problem.
We may spend the hour explaining and testing a concept, mapping a system, reviewing code, challenging assumptions, debugging, sketching an architecture or working an idea into a clearer form.
The aim is not simply to produce an answer for you.
It is to understand the problem well enough that the next decision becomes clearer — and that you leave with reasoning you can reuse.
When booking, send a short note about what you would like to work on. It can include a question, code, diagrams, documents, an existing system, or an idea that is still difficult to articulate.
I will review the context beforehand so we can spend the session on the problem itself.
If the work requires substantial preparation, research or code review outside the session, we can scope that separately in advance.
You do not need to be an engineer.
The Studio may be useful for founders, designers, product people, engineers, students, professionals adopting AI, or anyone trying to think more clearly about a technical problem.
Bring something worth thinking through.
I use Google analytics and ad-measurement cookies — on by default — to see what gets read and whether ads work. Decline removes them, leaving only cookie-free, non-identifying statistics. See the Privacy Policy. I use Google analytics and ad measurement. Cookies are set only if you accept — until then Google receives only cookie-free, non-identifying statistics. See the Privacy Policy.
