Source note: Originally posted from Eric's Advisory Hour Substack notes. Read the canonical note or subscribe to Advisory Hour.
A quick voice to text reminder for the participants that this would be a good week to rack up extra points by just doing multiple YouTube videos on one code related thing.
every YouTube video is something like 15 points… use that to your advantage… I will :)
The point of the reminder
This note was less about production polish and more about competition strategy. Week 2 was Tools for AI Tools, which meant a single code-related build could produce several strong pieces of proof: a walkthrough, a technical explanation, a demo pass, or a short lessons-learned video.
The scoring system made that behavior visible. If a YouTube video is worth meaningful points, the practical move is not to wait for one perfect artifact. It is to make the work legible while the work is happening.
Why it mattered for Spring into AI
Spring into AI rewarded shipping in public. The lesson for builders was simple: turn one code-related thing into multiple durable receipts, and the scoreboard starts reflecting the operating habit behind the project.
High-leverage proof-of-work
- One build can support multiple videos: setup, architecture, demo, failure mode, and follow-up iteration.
- Short public explanations compound: they help judges, competitors, and future readers understand what changed.
- Publishing cadence is part of the game: the competition measured visible execution, not just the final repo.
Original source
This local copy preserves the note text and source link for the Spring into AI build log. Canonical Substack note: https://substack.com/@advisoryhour/note/c-218519033.