The Format
This is not a syllabus. It's an operations order. Four days of in-person building with a week of real work in between. You will get stuck. You will debug things you don't understand at 9pm. You will ship something anyway. That's the curriculum.
Read this before you apply: This is not an academic program. There are no lectures. There are no slides. There is no "watch and take notes." You will be building from the first hour. If something breaks — and it will — you fix it. Dave is in the room to point you in the right direction, not to do it for you. The discomfort is the methodology.
Nobody shows up to Weekend 1 cold. The pre-work is not optional. If you haven't completed it, your seat becomes available to the next person on the list. The cohort does not wait.
You go home Sunday with something half-built. You stare at it Monday evening. You try four things. Three fail. The fourth works. You don't know exactly why it works. You dig until you do. That knowledge is yours permanently now. Nobody gave it to you. You found it.
Minimum: 1–2 hours per day. More if the project demands it. The milestone: by Thursday, the core feature of Phase 1 works end-to-end. Data in, data stored, automated response out. If it doesn't work by Thursday, Friday is for fixing it.
Some nights you won't feel like opening the laptop. The build isn't working the way you expected. You're not sure you picked the right problem. You wonder if the two weekends were a mistake. This is normal. This is the curriculum. Every builder has this week. The ones who push through it own the skill. The ones who don't were going to stop anyway. Post in the channel. You're not the only one.
Dave thought HomeSwerv was a six-week project. Hundreds of hours later it became a six-platform network. Not because the plan failed — because the foundation worked and the vision kept expanding. That's what happens when a real builder engages with a real problem.
Phase 1 deploys on Day 4. The parking lot is your roadmap. Phase 2 builds on your own timeline. The mastermind group keeps you honest. The co-working sessions keep you building. The community stays active because everyone in it has done the same hard thing.
Complete all four days. Build every day of the week between.
Do the work. If you leave Weekend 2 without a deployed Phase 1 application,
you get your money back.
Nobody has collected on that yet.
The Prompt Library
The prompt library is organized by role and tool. You are not guessing how to use Claude, Perplexity, or ChatGPT. You are running proven prompts that Dave uses in production — adapted for the problems you'll encounter during the bootcamp.
Design a Supabase data model for [X]. Show me the tables, columns, data types, and relationships. Explain the reasoning for each decision.
What is the market size for [X]? Who are the current players? What do customers complain about most?
This code is supposed to [do X] but instead it [does Y]. Here is the error: [error]. Here is the code: [code]. What is wrong and how do I fix it?
Create a simple, professional logo for [product name]. Style: minimal, modern, works on light and dark backgrounds. No text in the image.
Review this code for security issues before I deploy it. I am especially concerned about [X]. [code]
Act as a product manager. Define Phase 1 of [project]. What is the minimum version that proves the concept? What is NOT Phase 1?
Apply
8 seats. Application only. $4,500 solo, $7,000 for two. The only question left is whether you're ready to do the work.
dave@2weekai.com · responses within 24 hours