SSEL Embedded Systems Standard

Ivey's 12 Rules

1. Golden Rule: Write your code like you would like someone to write code for you
   • comments
   • flow charts
   • The two things that code must do is work and communicate.
2. Double checking a connection takes a lot less time (=money) than replacing a damaged component
3. Design for ESD - plan on ESD
   • zap your partner not your part
4. Keep RF out of your logic
5. Account for unused pins
   • Pull up/down resistors
   • especially in CMOS
6. Understand your test equipment
7. Design first, build later, test in stages, document always
8. If your microcontroller program doesn't work, there's a good reason
9. If your brain hurts, give it a rest
10. No spaghetti (code or wiring)
11. Get a clear requirement specification, if it isn't clear make it clear. Understand the requirements
12. Have fun