Claude and ChatGPT for Everyday Engineering Work
by Laura Mbeki
Your first month with model APIs: keys, streaming, retries, cost and one shipped feature.
PR Created by Priya Raman
Every bullet below is something you will have built, shipped or be able to explain by the time you finish the last lesson.
5 modules · 26 lessons · 3h 25m of material
5 lessons running 38m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
5 lessons running 42m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
6 lessons running 46m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
5 lessons running 40m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
5 lessons running 39m in total. Each lesson ships with the finished source files and a short written recap, so you can follow along in your own editor and skim the module again later.
Lesson-by-lesson titles, code downloads and exercises live inside the course library you get access to straight after checkout.
5 modules · 26 lessons
3h 25m total length
Short list, and deliberately so. If you meet these you can start today.
If you can write a web request, you can build with language models. What stops most developers is not difficulty, it is the fog of unfamiliar words and the quiet fear of an unexpected bill. This course clears both in an afternoon of focused work.
You set up API access properly from the first lesson, with keys in environment variables, a client wrapper you control, and spend limits configured before you send anything. Then you learn the request shape itself: messages and roles, the system instruction, temperature and maximum tokens, stop sequences, and how a response is actually structured when it arrives.
From there it is engineering. Streaming a response to a user so the interface feels alive, retrying with backoff when a request fails, handling rate limits without a crash, timing out cleanly, and logging enough to debug tomorrow. You calculate cost per request by hand until the arithmetic is second nature, then add a simple cache and watch the number fall.
The last third is a real feature built end to end: a document summariser with a queue, a status page and a proper error path. It is small on purpose, because the aim is a thing you have actually finished rather than a demo you have abandoned. Everything runs in Python, with a JavaScript version of each exercise included.
Still unsure about something? Write to misteryjj100@gmail.com and a human answers, usually the same working day.
Reviews are written by people who bought this course. We publish the critical ones too.
4.5
Rated 4.5 out of 5Course rating · 2 reviews
Gustavo Lima
Engineering manager
Working out what a feature will cost per thousand users before you build it is not something anybody taught me. Ten minutes of multiplication in this course has already stopped me building something I could not have defended in a budget meeting.
Mia Fontaine
Web developer
Everything through streaming and retry handling is pitched exactly right for a beginner, and building your own thin client rather than reaching for a framework was the correct decision. The feature you ship at the end is quite small though, and I would have taken one more chapter on it over anything else.
Applied AI and machine-learning engineer
Priya builds language-model features for a document-heavy SaaS product, which means she has taken retrieval and fine-tuning from a promising notebook to something on call at three in the morning. She teaches the mathematics only where it changes a decision you are about to make, and spends the rest of the time on data quality, evaluation and the cost of an agent that loops. Her courses run on a laptop and a modest API budget, so nobody has to rent a cluster to follow along. She publishes reproducible notebooks alongside every module.
One-time payment · lifetime access