Make It Real
Interfaces, APIs, databases, security and deployment
This is the night the boxes connect. Instead of memorizing definitions, you submit real data, watch the network request, inspect the database row and debug the failure points with the agent beside you.
Dates TBD — evening workshops followed by a longer capstone hackathon at Workuity Biltmore. Join Discord or follow the Meetup calendar for the next cohort.
Or join the waitlist — the dates come to you.
Venue sponsor: Workuity. Format: the host builds live on screen. Bring a laptop and work along, or just watch — nobody is put on the spot.
Why this session
Most vibe-coded products break at the seams: the interface looks finished, but the API, data model or deployment assumptions do not hold. Knowing how information travels through the system lets you ask better questions and recognize when the answer is wrong.
What we cover
- 01
The browser and the server
What belongs in each place, how a request crosses the boundary and why secret keys never belong in frontend code.
- 02
APIs and JSON by watching one
Read the method, URL, headers, body, JSON response and status code in the browser's network panel instead of memorizing an abstract diagram.
- 03
CRUD and a database that matches the product
Tables, rows, IDs and relationships; design the smallest useful schema, then create, read, update and delete a record through the app.
- 04
Connect and inspect the full path
Submit the form, watch the request, inspect the saved row and render it back in the interface with loading, empty, success and error states.
- 05
Secure the seams
Keep keys server-side, validate input on the server, enable database access rules, verify webhook signatures and run a short pre-ship security checklist.
- 06
CI/CD, deploy and debug
Push the repository, let automated checks gate the deploy, set environment variables and fix the first production-only error from its logs. A supplied automation is the optional extension.
You leave with
A deployed full-stack product with a form-to-API-to-database path you can explain, inspect, secure and debug.
To follow along
A laptop and the repository from session one. You will need accounts for GitHub and the selected hosting and database services. The setup guide will name those services, any free-tier limits and any expected usage costs before the session.
Afterward
Nothing is required. It compounds if you run the same work on your own product. The suggested output:
02-full-stack/ — live URL, data-flow diagram, schema notes, security checklist and evidence of one successful push-to-deploy run.
Everything is open source. Missed the session? It's archived in Discord.
The session kit
Slides, a follow-along guide and skill files. Free to download, room or no room.
The community online
Recaps, archive links, questions between sessions, everyone else's work in progress.