Build real learning software for your team. No development background required.
Fifteen hours, live. You, Claude Code or Codex, and Peck, the workspace that handles the setup. You leave with your own app deployed, for your team or for yourself.
Join the waitlist
Free to join, no payment now. We'll email you when enrollment opens, and waitlist members get first access. Unsubscribe anytime.
- 15 hoursLive, over four sessions
- 30 seatsFounding cohort, capped
- $1,999Founding price, or 3 × $699
- Mac or WindowsWith a Claude or ChatGPT plan
Your app. Deployed.
You bring a real problem: something your team needs, or something that would help you. Over the weekend you build it with an AI coding agent, put it on the internet, and demo it at Thursday's showcase.
You build inside Peck, our desktop workspace for Claude Code and Codex. It sets up the project, the container, and the guardrails, so your first hour goes to your app instead of to installing tools. Peck is in early beta: it's the workspace our own team builds in every day, and you'll be among the first outside it.
See PeckA few ideas people bring
Practice and feedback coach
Learners respond to a scenario and get feedback against your rubric.
Knowledge-check generator
Paste source content, get draft questions, edit them, export to your LMS.
Onboarding portal
One place for a new hire's first weeks, with progress you can see.
Job-search assistant
Track applications, sharpen your portfolio pitch, prep for interviews.
The AI builds while you learn
We start with the concepts and building blocks you need: what a repository is, what a container is, how to tell an agent what to do and check what it did. Then builds kick off as the group wants to see them, and the teaching continues while the agents work. The waiting is the lecture.
Sessions run live in our own workshop platform, not Zoom: breakout rooms for pairing, and a quick swap between lecture and discussion when a question needs the whole room.
The building blocks of a learning engineer
- 01
Peck and dev containers
What a container is, why your project lives in one, and when to step outside it.
- 02
GitHub in plain language
Repositories, commits, branches, and pull requests, for people who've never used them.
- 03
Working with Claude Code and Codex
How to brief an agent, read what it did, and keep it on track.
- 04
Context management
What the model can see, what it forgets, and how to keep a long build coherent.
- 05
Choosing a model
Which model for which job, and what each one costs.
- 06
MCP servers
Connecting your agent to tools and data it can't reach on its own.
- 07
API keys and secrets
Where keys live, where they must never go, and how to rotate one.
- 08
Databases and hosting
Supabase for data, Vercel for deploys, and how the two fit together.
- 09
Sign-in and row-level security
Adding accounts, and making sure people only see their own data.
- 10
Learner data, privacy, and accessibility
What not to store, where personal data goes, and the accessibility basics every learning tool needs.
- 11
Shipping and maintaining it
Deploying, updating without breaking things, and knowing when you're done.
Four sessions, one week
- 3 hours
Friday, January 22
Setup and the building blocks: Peck, GitHub, and your first working build.
- 5 hours
Saturday, January 23
Your app takes shape: data, sign-in, and the agent workflow that keeps it moving.
- 5 hours
Sunday, January 24
Deploy, secure, and polish. You leave with a live URL.
- 2 hours
Thursday, January 28
Showcase. Everyone demos what they built and what they learned.
Tentative. Times of day are confirmed with the waitlist.
Three things, and we handle the rest
- A paid Claude plan or a paid ChatGPT plan
- A Mac or Windows computer
- A free GitHub account
Setup happens in session, together.
This is the founding cohort price. Waitlist members get first access when enrollment opens.
Join the waitlistWho it's for
This is for you if…
- You work in L&D or instructional design and have a problem you'd solve if you could build
- You're an aspiring instructional designer who wants to stay ahead of the tech curve
- You're comfortable being early: Peck is in beta, and you'll help shape it
- You can attend all four sessions live
This might not be the fit if…
- You want a no-code template to fill in
- You want a full software-engineering course
- You can't attend live
Frequently asked questions
No. You need to describe what you want clearly and check whether it works. The agent writes the code; you learn to direct it, read what it did, and keep it honest.
A paid Claude plan (for Claude Code) or a paid ChatGPT plan (for Codex). Either works. If you don't have one yet, the waitlist survey will help you pick.
Peck is in early beta. It runs on Mac and Windows, but not every setup is covered yet. If it doesn't run for you, we'll get you set up another way during the Friday session so you're not left behind.
Yes. Every session is recorded, so you can catch up on anything you miss. Plan to attend live, though: most of the value is in building alongside the group and getting help in the moment.
Yes, if you want to build. A job-search assistant, a portfolio tool, a practice app for yourself: the skills are the same, and so is the result. Something real, deployed, that you made.
No. The intensive is separate from the Foundations, Practitioner, and Professional programs.
Someone who designs learning and can also build the software that delivers it. This intensive is the first step: it's how we find out what a longer program should look like.
After we survey the waitlist and confirm the plan. Waitlist members hear first.