Last week was pure reading — count, merge, shape. This week each function reads and then thinks: longest snippet, events containing a keyword, counts per bucket. And mid-week you wrap the read calls in try/except so one dead API never kills the function.
So every lesson still starts with two execute_action calls, and the new work lives after the fetch — filters, sorts, group-bys? Where does try/except land in that flow?
Fetch, protect, transform. Day 10 sorts email snippets by length. Day 11 filters calendar events by a keyword. Day 12 groups emails into buckets. Day 13 is the defensive lesson — try/except around a two-API function so a partial result still reaches the caller. Day 14 picks the busier source. Same skeletons, smarter bodies.
And the try/except lesson means my multi-API functions stop caring which API goes down — one half always works?
A half-response is still a response. By Friday you can analyse two live sources and survive one of them misbehaving. That is the shape every production automation needs.
Goal: Read, analyse, survive failures — the three muscles every real pipeline needs.
Create a free account to get started. Paid plans unlock all tracks.
Last week was pure reading — count, merge, shape. This week each function reads and then thinks: longest snippet, events containing a keyword, counts per bucket. And mid-week you wrap the read calls in try/except so one dead API never kills the function.
So every lesson still starts with two execute_action calls, and the new work lives after the fetch — filters, sorts, group-bys? Where does try/except land in that flow?
Fetch, protect, transform. Day 10 sorts email snippets by length. Day 11 filters calendar events by a keyword. Day 12 groups emails into buckets. Day 13 is the defensive lesson — try/except around a two-API function so a partial result still reaches the caller. Day 14 picks the busier source. Same skeletons, smarter bodies.
And the try/except lesson means my multi-API functions stop caring which API goes down — one half always works?
A half-response is still a response. By Friday you can analyse two live sources and survive one of them misbehaving. That is the shape every production automation needs.
Goal: Read, analyse, survive failures — the three muscles every real pipeline needs.