From Buzz to Build
A Learning Lunch about AI-Assisted Development
What changes. What stays. And why you should just try it.
Press Arrow Right to begin — or F for fullscreen
Tools are popping up like mushrooms in the forest. We're living through the most rapid tooling evolution in software history.
Consolidation will come. But right now? Experiment. The landscape rewards the curious.
"Person who types code in IDE"
Focus on syntax, boilerplate, gluing APIs, scaffolding projects
"Product thinker who validates hypotheses at the speed of thought"
Focus on context, requirements, architecture, business value
20 years of agile adoption. We have the ceremonies. Do we have the values?
AI doesn't fix bad process — but it removes the excuse. When you can prototype in hours, "we need 6 months" sounds... different.
AI is our best tool for fast validation. Build prototypes good enough to test business assumptions — without building the silver-bullet solution first.
A friend built a full family agenda web app over a single weekend.
Another friend built a scheduling SaaS for his spare-time hockey team. Side project to product.
Full IaC-based open-source cloud stack: multi-tenancy, management UI, carrier-grade network isolation. VMware replacement, deployable in 30 min.
These aren't Fortune 500 projects. These are curious people with an idea and an AI assistant.
Not technically — methodically.
AI is powerful. It's not magic. Understanding the boundaries makes you a better user.
Tools like Claude Code don't just suggest — they read your codebase, run commands, create files, and iterate on errors. Qualitatively different from autocomplete.
AI that interacts with your actual systems: databases, APIs, CI/CD, infrastructure. Model Context Protocol is making this standardized and interoperable.
Decentralization and democratization of AI. Run models locally with Ollama, fine-tune for your domain, keep data sovereign.
Don't paste production secrets into AI. Understand your data policies. Use enterprise plans or local models where sensitive data is involved.
No clear "learning path". No "use tool X, don't use tool Y".
Just be curious. Start a pet project. Break things. Learn.
It doesn't have to be for work. A hobby project. A family tool.
A weekend experiment. The barrier to entry has never been lower.
What you're looking at right now was built by an AI assistant (Claude Code) in a live coding session. Here's what happened:
Total time from zero to deployed: one evening of vibe-coding with Claude Code.
Questions? Ideas? Let's chat.
Start today: claude.ai | chatgpt.com | ollama.com
This presentation: built with Astro + Claude Code
Source & slides available after the session