Past session · Wed, Sep 2

The project you haven't opened in two weeks.

Something broke, and the folder's been sitting there since. That's week two, not a verdict. A free 60-minute session on getting a half-built project over the line. Learn what to cut, what to hardcode, and what "done" actually means when the deadline is Sunday.

Recording availableAired Wed 2 Sep · 8:00 PM EAT

500+ developers already learning together every week

What the hour looks like

No slides read aloud. A feature, built.

The session in three movements — watch it happen live, then do it yourself with the template.

app/api/ai/route.ts

// live: shipping an AI feature

const ai = new Anthropic();

export async function POST(req) {

const { prompt } = await req.json();

const stream = await ai.messages.stream({

model: "claude-sonnet-4-6",

messages: [{ role: "user", content: prompt }],

});

return stream.toResponse();

}

Forty minutes of live coding — a real feature on a real Next.js app.

COST / 1K REQUESTS

GPT-4 CLASSKES 1,940

CLAUDE SONNETKES 1,290

OPEN-SOURCE (HOSTED)KES 610

ILLUSTRATIVE — WE PULL THE REAL NUMBERS LIVE

The per-request costs nobody puts in the tutorial.

PRE-FLIGHT

Streaming responses working

Fallback when the API is slow

Spend alerts before the surprise

Template pushed to registrants

DEPLOYED · LIVE

You leave with the template — and your questions answered.

Save my seat — it's free

What you'll leave with

Worth sixty minutes of your Wednesday

A working definition of done

One thing works, end to end, for one person. Enough to submit.

A list of what to cut

The feature you added after you started is usually the one that broke it.

Something on a live URL

Deployment as a decision, not a tutorial. No domain needed.

Permission to submit something rough

Hardcoded, ugly, one route. It has to run, not impress.

Run of show