The four beats
Build it, take it apart, extend it, ship and post. Every build chapter in nine phases runs this loop.
Click round the loop. Every build chapter in this course runs these four beats in this order, so it is worth knowing what each one asks of you.
01 · Build it
beat 01- You
- Ask for the whole thing in one go and get it running in front of you.
- Your AI
- Writes the first version, including the parts you could not have written yet.
- Actually learned
- That shipping is the starting line. Everything after this has something to point at.
Every lesson in all nine phases runs these four, in this order. Beat four feeds beat one of the next lesson, which is why the diagram is a ring and not a checklist.
Beat one gets something concrete on the screen. Nothing is graded here. It simply gives beat two something to examine.
Beat two is the teardown, where most of the learning happens. Delete a line, watch what breaks, then put it back. Once you can explain why a decision exists, you are more likely to make that decision intentionally next time.
Beat three needs decisions that only you can make, such as your radius scale, error contract or latency budget. This is where you stop simply accepting the model’s defaults and start directing the work.
Beat four is deploying and writing it up. It may look like admin, but it is part of the practice. You will ship around forty times across the course instead of waiting until the end to do it once.
You should now be able to
- Explain why beat three cannot be one-shot by a model
Loading…