Came across this the other day, an explanation for how SQLite stays almost bug-free.
Super basic overview:
- Write comments about how things work to engage the linguistic side of your brain
- 100% test coverage, including all possible branches (test suite will run every single line of code at least once)
- When you find a bug, fix the process that lead to the bug.
Overview (full talk in pdf linked in post):
http://aleccolocco.blogspot.com/2009/08 ... tware.html
Sounds like a great development methodology for the internal Tuner libs, also seeing some of the gcc testing stuff in the pdf - could be alot of use in the firmware too!
SQLite development methodology
- sry_not4sale
- LQFP144 - On Top Of The Game
- Posts: 568
- Joined: Mon Mar 31, 2008 12:47 am
- Location: New Zealand, land of the long white burnout
- Contact:
SQLite development methodology
Owner / Builder: 1983 Mazda Cosmo 12at (1200cc 2-rotor turbo) coupe [SPASTK]
165hp @ 6psi standard - fastest production car in japan Oct 82
165hp @ 6psi standard - fastest production car in japan Oct 82