By Kevin McAleer, 3 Minutes
Page last updated November 21, 2026

You started this course with an editor. You’re finishing it with a workshop.
| Tool | What it’s for | Where |
|---|---|---|
| Autocomplete and signature help | Writing without looking things up | As you type, Ctrl+Space |
| Hover and Help for symbol | Reading documentation in place | Mouse, right-click |
| Go to Definition | Following code to where it’s defined | F12 |
| Find and Replace | Changing many places at once | Ctrl+F |
| Problems panel | Seeing every finding in one list | Bottom panel |
| Refactoring hints and Tidy | Smaller, faster MicroPython | Lightbulb, right-click |
| YAML and JSON validation | Settings files that load | Automatic |
| Packages | Installing libraries with mip | Activity bar |
| Modules | Seeing what’s already on the board | Packages, Modules tab |
| Compile to .mpy | Less memory, faster start | Right-click a file |
| Source Control | History, diffs and undo | Activity bar, desktop |
| Chat | Explanations and first drafts | Editor top right, desktop |
The tools are most useful in an order:
Steps 1 and 6 are the ones people skip, and the ones they wish they hadn’t.
Let the editor remember things. You don’t need to memorise every method of every class. You need to know how to ask.
A hint is a lesson. Every refactoring hint has a Why? article. Reading them is a short course in how MicroPython really works.
Make changes you can undo. Preview before applying. Commit before experimenting. Then nothing you try can cost you more than a few minutes.
Quick quiz 1 of 3
Your robot worked yesterday and doesn’t today. Which tool do you open first?
Quick quiz 2 of 3
A program fails with MemoryError while importing a large library. What might help?
Quick quiz 3 of 3
Before installing a library, where should you look?
You can use the arrows ← → on your keyboard to navigate between lessons.
Comments