Final Projects
Notes, Tips, and Tricks
Notes, Tips, and Tricks
Lessons from the Hackathon
Power issues
Hardware connection issues
Hardware failure issues
Communication issues
Permanent joints >.<
Uploading errors?
Code logical errors?
Not using serial monitor for debugging >.< >.< >.<
How to spot a bad developer?
Perfectionist: won't start without a full specification with every smallest detail
Overconfident: not open to any guidance or criticism
FreakOutKermit: freaks out when something fails
HawaiiGuy: I'll work when I'm in the mood
Theorist: everything is easy -in theory- for him
StackOverflow: copy-paste codes without understanding what happens
CommunistBugsBunny: copies your code cause its opensource
ComfortZoner: does the minimum. avoids risks and long tracks
Things To Do
Know the limits: Time - Budget - Effort
Work in Spirals
Divide and Conquer
Save versions of your working code
Ask google before you ask for help
Test components.. Don't trust them :D
Wire before power
While Working in the MakerSpace
Keep the place clean
Return the tools to their place
Don't mix your components with someone else
Don't use any type of Glue
Don't use the box Maker
Arranging Your Timeline
Starting From CAD
Starting From Electronics
Going Hybrid
Library