Automate the report. Keep the hours.

No, and the course assumes you aren't. The starting point is Excel: the first real moment is seeing a VLOOKUP become a single line of code, because that's the thing you already understand deeply. Every line of code you're given comes with a plain-language explanation of what it does — not one unexplained line for the whole thirty days.

AI writes most of the code, and this leans on that heavily rather than pretending otherwise. What it can't do is run on your machine, know your column names, notice that your numbers came out wrong, or fix it when a campaign name with a comma breaks the file. Those are the actual skills here — enough Python to direct, check and repair generated code. People who skip that step end up with scripts they daren't run on anything that matters.

No, and it's one of the first questions you're asked. There are browser-based options that need nothing installed and work fine for reading your exports and building reports, plus portable setups that don't touch system permissions. The setup step works within your constraints instead of recommending things you'd have to argue with IT about.

That's the design, not the minimum. The whole plan is built as thirty short sessions, each ending with something visibly working, because a course structured around three-hour weekend blocks is a course that dies in week two. Daily also matters more than total time — code you touch every day stays readable to you, and code you visit weekly has to be relearned each time.

Yes, and you say where your data lives before anything else so the setup matches. CSV and Excel exports are the simplest starting point and where most people begin. Pulling directly from an API is the natural next step once the basics are working, and it's one of the options for what to build after your first report.