Your toolkit is set
Three chapters ago you'd never opened a terminal. Now you have a terminal you can move around in, and two AI building tools installed inside it, signed in, and run at least once each. That's a real starting toolkit, and it's complete enough for everything the rest of this course asks of you.
Just as important, you have the judgment that goes around the tools:
- You know a terminal AI tool runs a look-plan-act-check loop.
- You know it asks before it changes things, and that reading the line is your job, in every tool, every time.
- You know the working habits: ask for the plan first, one job at a time, stay and watch.
- You know there's no single best tool, and you have concrete reasons to switch between the two you've got.
What comes next
From here, the course stops teaching the tools and starts teaching you to build with them. You'll learn to read the Python that these tools write, because a tool that writes code you can't read is a tool you can't direct or correct. You'll learn what these models get wrong, and how to catch it. You'll learn to give them better instructions, to check their work, and eventually to build your own small tools on top of them.
The two CLIs will be there the whole way. They stop being the lesson and become the workshop. Every chapter after this one, you'll have a terminal open and a CLI ready, and the thing you're learning will be something you build with them, not something about them.
You walked through the door. Now the course is the building.
Your toolkit is set
Three chapters ago you'd never opened a terminal. Now you have a terminal you can move around in, and two AI building tools installed inside it, signed in, and run at least once each. That's a real starting toolkit, and it's complete enough for everything the rest of this course asks of you.
Just as important, you have the judgment that goes around the tools:
- You know a terminal AI tool runs a look-plan-act-check loop.
- You know it asks before it changes things, and that reading the line is your job, in every tool, every time.
- You know the working habits: ask for the plan first, one job at a time, stay and watch.
- You know there's no single best tool, and you have concrete reasons to switch between the two you've got.
What comes next
From here, the course stops teaching the tools and starts teaching you to build with them. You'll learn to read the Python that these tools write, because a tool that writes code you can't read is a tool you can't direct or correct. You'll learn what these models get wrong, and how to catch it. You'll learn to give them better instructions, to check their work, and eventually to build your own small tools on top of them.
The two CLIs will be there the whole way. They stop being the lesson and become the workshop. Every chapter after this one, you'll have a terminal open and a CLI ready, and the thing you're learning will be something you build with them, not something about them.
You walked through the door. Now the course is the building.