Arduino Dojo @Mozilla

Slides used to present a Coding Dojo with Arduino at the Mozilla offices in San Francisco

Transcript

1. presentS
2. arduINO CoDIng dOjo
3. coding dojo * Collective programming exercises * Fun and effective for: * Introducing best practices; eg.TDD * Learn languages and APIs * Welcome new team members
4. arduIno for the dojo
5. randorI: Free practice * Pair programming with TDD * One pair: pilot and copilot * Pilot types * Copilot assists * After 5 minutes pilot steps down * Copilot become pilot * Volunteer becomes copilot
6. tdd = test-driven design * Write test before adding any new funcionality * While test is not passing, audience should be quiet * When test passes, audience may give suggestions for next steps
7. tdd wITh hardware? * Objective, testable steps must be written *before* new code is added * It’s hard to automate hardware tests; more hardware would be needed * In the Arduino Dojo we do manual/visual testing
8. babY steps * Each step should be so simple the implementation is obvious * Just enough to pass the test * Resist the temptation to be clever and optimize or generalize before the next test is passing
9. Example: First Step * Blink the led connected to pin 13 * To check USB connection and “smoke test” the circuit under testing
10. today’s problem * Make a simple animation toggling the 6 LEDs in the perimeter of the display in sequence, at a rate controlled by the pot
11. 7 segment display pot Arduino
12. STArt! * Volunteers? * If a new copilot volunteer does not step up in a timely manner, the randori may end prematurely * I have 150 slides about the History of Cobol to show instead
13. Come visit US in São Paulo, all Are Welcome! http://garoa.net.br