In this mini-book we will use a series of exercises to discover a few possibilities of Arduino.If you have never worked with Arduino, I recommend that you read our glossary before you begin the exercises. (It is of course your choice how you want to learn.)Programming mainly means looking for errors. Especially to help you with this, we have a chapter with tips for finding errors.This workshop consists of 10 exercises. Every exercise has the same format: * Assignment* Material* Connecting* Code* Possible mistakes* ExpansionFor the expansion, the idea is to do them without looking at the solution. If you do a workshop with me, you will only receive the solution for the expansions at the end of the workshop. These solution are in the book, my intention is that participants of the workshop can solve these parts themselves. This way they are better prepared for the rest of the exercises. If you read this book on your own, when you make the exercises in this book, I hope you will not look at the solution of the extensions, I'm convinced that that way, you learn faster. To help you during the exercises, it is best to save your code a lot.What I always do, is make a copy of the code at the start of an exercise (or extension).In other words save as exercise1.ino and extension1.ino. And while I am busy with the exercise, save regularly and save with that name again at the end of the exercise. (You can also use exercise1_Begin.ino and exercise1_End.ino)When I do that, I can always return to the code of that exercise.Real programmers use a source control system (like github) for that, my way, is our poor person source control system. Programming is not easy. Even the smartest developers are regularly stuck. They are asking for help to other programmers, are programming with two (PairProgramming) or looking for help on the internet. So when you don't immediately know what to do, that does not mean you are stupid. It means you are learning. People that program are always learning. That's because developers are usually creating something that does not exist. That means that as a developer, you will think regularly: damned, I don't know (how to do this). The smartest programers ask a lot for help. Because they know, by asking for help, they learn something.I hope you have as much fun with learning arduino as I do.GreetingsGeike Hanoull