Block 1 · Week 2 · Building APIs and the backend
Building APIs and the backend
As an FDE you work inside a customer's stack, wired to machines someone else built. When one breaks on site, you need to be the driver, not the passenger.
A passenger enjoys the comfort of a car. A driver understands its controls and knows what to do when things go wrong.
Comfort without understanding comes at the cost of control.
In software, SDKs, libraries, no-code/vibe-coding tools are like comfortable passenger seats. They make the journey easier by hiding the machinery underneath.
But hidden machinery doesn't disappear.
When something breaks, what you understand determines what you can fix.
To drive software machines, understand its controls: APIs, endpoints, authentication, requests, and responses.
Use abstractions for comfort. Build understanding for control.
01
Your path this week
- Send the raw request in the browser
- Rip off the cushion in Python
- Verify against your golden pair
- Gather your deliverables
02
When you need it
Read
Notes
Do this
Practice set
Stuck
Troubleshooting
Roadmap
Back to the roadmap
Refresher
The second interface · Groq step
Guide
Keys
A 200 means the machine understood you. It does not mean you helped anyone.Next: building your own API, and how much protection it actually needs.