Last track you wrote single-source functions — count Gmail, find an event, create a task, one API at a time. This week you combine them. Every function this week reads from at least two APIs and returns a single shape.
So every lesson has me making two toolset.execute_action calls back-to-back and combining the results? Is the hard part the calls, or the shape of what I return?
The calls are the same skeleton you already know — action enum, params dict, response dict. The new skill is shape: you'll decide whether two counts go into a dict, a tuple, or a formatted string. Day 3 counts inbox + events. Day 4 picks the bigger source. Day 5 unifies snippets. Day 6 combines titles. Day 7 is a morning overview that ties the week together.
And everything still hits my real Gmail and my real calendar? The numbers the tests print are my live data?
Live inbox, live calendar, every run. By Friday the three-line skeleton from last track becomes a six-line skeleton across two APIs — and you'll see the same shape stick for the rest of the month.
Goal: By Friday you can write a two-API function without looking up a single action name.
Create a free account to get started. Paid plans unlock all tracks.
Last track you wrote single-source functions — count Gmail, find an event, create a task, one API at a time. This week you combine them. Every function this week reads from at least two APIs and returns a single shape.
So every lesson has me making two toolset.execute_action calls back-to-back and combining the results? Is the hard part the calls, or the shape of what I return?
The calls are the same skeleton you already know — action enum, params dict, response dict. The new skill is shape: you'll decide whether two counts go into a dict, a tuple, or a formatted string. Day 3 counts inbox + events. Day 4 picks the bigger source. Day 5 unifies snippets. Day 6 combines titles. Day 7 is a morning overview that ties the week together.
And everything still hits my real Gmail and my real calendar? The numbers the tests print are my live data?
Live inbox, live calendar, every run. By Friday the three-line skeleton from last track becomes a six-line skeleton across two APIs — and you'll see the same shape stick for the rest of the month.
Goal: By Friday you can write a two-API function without looking up a single action name.