MarmicodeCharted Coding: AI-Assisted Development Without the Drift
1 Day · Online
🐣 Early Bird starts at €390
One day to move from fast-but-fragile AI coding to approaches you can sustain.Map Vibe Coding and Spec-Driven Development — then chart a path your architecture can live with.
🍱 What you will learn
Contrast Vibe Coding and Spec-Driven Development (Spec Kit, BMAD, OpenSpec, etc.) and tie them to a structured, test-driven approach.
Choose an AI-assisted workflow suited to prototypes, production features, greenfield, brownfield, or legacy code.
Write design documents that work for both humans and agents — without drowning in over-specification.
Align your intent with the code produced using tight iteration cycles.
Steer clear of drift, loss of control, over-engineering, review fatigue, and multitasking distraction.
Integrate these practices into daily workflows and clarify collaboration patterns around tests, prompting, and review.
Token spend is just the start. Cut the hidden costs: steering, reviewing, and rejecting AI output.
🗓️ Program
- Defining “Vibe Coding”.
- When it works (and why it is appealing).
- Classic pitfalls: drift, maintainability issues, illusion of productivity.
- Iterate with Vibe Coding on the initial feature.
- Cool-headed analysis: what holds up and what breaks.
- The Spec-Driven approach: Spec Kit (GitHub), BMAD, OpenSpec, and alternatives.
- Anatomy and inner workings of Spec Kit.
- Revisit the same use case with a spec-driven workflow.
- Pros and cons — lessons learned.
- Strengths and limitations of each approach depending on context.
- When Vibe Coding is enough — and when it becomes dangerous.
- When Spec-Driven pays off — and when it becomes a drag.
- Navigating with a map rather than drifting: steering the agent while keeping control of the trajectory.
- Co-building a pragmatic “Design Doc” with the agent — and orchestrating review by specialized agents.
- The Scaffold → Red → Green → Refactor cycle.
- Tests as executable specification and as the AI agent’s feedback loop — how this differs from classic TDD.
- Compatibility with your current stack (Vitest, JUnit, pytest, etc.) — framework-agnostic mindset.
- Introduction to Charted Coding.
- Iterate on the common use case using the incremental method.
- Extending the method with Skills and MCP servers.
- Integration with OpenSpec.
- Practice the incremental approach with OpenSpec integration.
- Integrating the method into an existing team workflow.
- Collaboration patterns: who writes the tests, who drives the AI, who reviews.
- Choosing the right approach for the task at hand.
- Q&A and feedback from participants.
🎓 Required knowledge
- Development experience in a typed language (TypeScript, Java, C#, Python with types, etc.) — exercises use TypeScript
- Familiarity with automated testing
- Prior use of an AI assistant to generate code (Copilot, Cursor, Claude, etc.) — occasional use is sufficient
👨🏻🏫 Your instructor
Younes Jaaidi
I am a Software Cook who enjoys whipping code until tests pass.
With nearly 20 years of experience in eXtreme Programming, I've coached dozens of teams and trained thousands of developers to cook robust and maintainable software — using Test-Driven Development, pragmatic testing strategies, and a healthy dose of Collective Ownership.
I'm also an Angular Google Developer Expert, an NX Champion, and a mediocre sailor.
🙋 Frequently Asked Questions
Developers using or wanting to use AI assistants effectively; leads and tech leads framing AI usage; architects and CTOs industrializing AI-assisted development without sacrificing quality; and teams struggling with drift in generated code who want a structured, reproducible approach.
You should be comfortable in a typed language (exercises are in TypeScript), familiar with automated testing, and have tried an AI coding assistant at least occasionally.
A computer with internet access, microphone, webcam, an up-to-date browser, installation rights, and a working AI assistant (Copilot, Cursor, Claude Code, or equivalent).
Yes. You will practice throughout the day on a common use case, compare approaches directly on the same problem, and leave with a collective synthesis and an individual action plan.
No. The principles apply across stacks; tests as executable specification are illustrated with patterns compatible with Vitest, JUnit, pytest, and similar runners.
Yes. Contact me for a quote and administrative details.
"Book a Session" lets you join a scheduled session with other participants. "Custom Session" is for companies who want a private, in-house workshop — with optional adjustments to content, duration, or focus areas.
If the workshop doesn't meet your expectations, reach out within 7 days and we'll work it out.