Three weeks of reads, writes, chains. This week every function assumes something will break: the API is slow, the input is bad, a field is missing. Defence lives inside the function, not in the caller — and Friday is the capstone that ties it all together.
So every lesson this week adds one defensive pattern on top of a script I could already write? Try/except, fallback, validation, dedup, then the capstone?
Day 24 wraps the Gmail read in try/except. Day 25 builds a generic count-with-fallback that works across any action. Day 26 is a full email-to-task pipeline with per-item guards. Day 27 validates inputs before any write fires. Day 28 is the capstone — one function, three APIs, every defensive pattern baked in.
And the capstone ships as a real script I could drop into a cron job — no manual testing, no hand-holding?
One cron-ready function by Friday. Reads two APIs, writes to one, survives a failure in any of them, hands back a receipt the caller can log forever. That is the finish line for this track.
Goal: Ship a cron-ready function by Friday — reads, writes, and survives failures.
Create a free account to get started. Paid plans unlock all tracks.
Three weeks of reads, writes, chains. This week every function assumes something will break: the API is slow, the input is bad, a field is missing. Defence lives inside the function, not in the caller — and Friday is the capstone that ties it all together.
So every lesson this week adds one defensive pattern on top of a script I could already write? Try/except, fallback, validation, dedup, then the capstone?
Day 24 wraps the Gmail read in try/except. Day 25 builds a generic count-with-fallback that works across any action. Day 26 is a full email-to-task pipeline with per-item guards. Day 27 validates inputs before any write fires. Day 28 is the capstone — one function, three APIs, every defensive pattern baked in.
And the capstone ships as a real script I could drop into a cron job — no manual testing, no hand-holding?
One cron-ready function by Friday. Reads two APIs, writes to one, survives a failure in any of them, hands back a receipt the caller can log forever. That is the finish line for this track.
Goal: Ship a cron-ready function by Friday — reads, writes, and survives failures.