Past session · Wed, Sep 23

Your feedback contradicts itself. Now what?

One user asks for a feature. The next one says that same feature confused her. A third wants something you would never build. A free 60-minute live session on sorting the messages sitting in your DMs. Now you are wondering what to build, what to note, what to ignore, and how to say no to a user without losing them.

Recording availableAired Wed 23 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 filter for contradictory feedback

Three messages that disagree, and a way to decide which one gets built the same way the three columns decide which features stay.

The difference between polite and useful

"Looks great" from someone who never came back versus "I got stuck here" from someone who did.

The problem hiding in a request

Hearing "add a button" and finding the slow step or the lost user behind it.

A way to say no

Turning down a request without the user walking away.

Run of show