Day 4: Paste, save, and resist the urge to "understand" it all


[This is Day 4 of 5.]

Today you'll open a file called index.html (the dashboard's front page) and paste in the URL and API key you saved yesterday. Two lines. That's the whole task.

A note about safety here: the API key is visible here together with the URL. As a result, they are technically visible to people on the internet. As a result, do not put PII or sensitive info in your to do list as it may be visible to those who search (unlikely but safety first!). In a subsequent exercise another week, we'll work through building something where the API keys MUST remain hidden and how that works.

Back to the building, you don't need to understand the code to use it. You drive a car without knowing how the engine fires. Same deal. Claude wrote this; your job is to drop your two keys in the right spots, which I've marked clearly.

If you hit a snag (a quote in the wrong place, a line that looks off) don't spiral. Copy the file, paste it into Claude, and say "I pasted my keys here, something's wrong, what did I miss?" That's not cheating. That is the skill. Knowing how to ask the machine to debug itself is more valuable than memorizing syntax. Asking Claude is always the hack.

You're one step from a working dashboard. You can feel it now.

👉 Today's steps: Step 4​

Tomorrow: we flip the switch and put it online.

Alex

AZAI Advisory

As an AI Coach, Advisor, and Agent Builder, I help organizations and business leaders harness the power of artificial intelligence to boost productivity and streamline operations. I enable organizations to navigate the transformative landscape of AI, educating teams, identifying operational and strategic opportunities with AI and creating a framework for safe and transparent use of data in the organization.

Read more from AZAI Advisory

Aaron Levie, the CEO of Box, posted this week that he’s seeing “productivity gains that are an order of magnitude or two above output levels pre-AI.” An order of magnitude or two. That’s 10x to 100x. He was reacting to a post from developer Theo Browne about the gap between average and great engineers, and his point is a good one. People who had deep expertise before AI, and who are willing to work differently now, are pulling further ahead. He thinks finance, science and cyber are next. Then...

Last week I asked a nonprofit executive director about her biggest pain point at work. Her answer: her to-do list. It lives in eight or more places. Email, calendar, meeting notes, and a separate email thread for each of her direct reports, where team notes pile up between one-on-ones. There's no single place she can look and see everything she owes everyone. If you run a team, you probably recognize that list. (I certainly do.) We looked at two options together. The first is an automated...

Here's a study worth reading before you sign your next memo. On Oct 27, Anthropic published a study called "How AI agents shape experts' judgment calls." Here's what they did. They asked 50 professional analysts, all experienced in working out cause and effect from data, to advise a farming cooperative. The question: is the co-op's advisory program working well enough to expand? Each analyst worked with Claude Code. Along the way, the analysts had four judgment calls to make, each with two...