Scroll down
If you can read this, thank a Software Developer.
It's not a bug - it's an undocumented feature.
With enough practice, any interface is intuitive.
Hindsight is an exact science.
One person's data is another person's program.
Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code.
Fast, good, cheap: pick any two.
If the code doesn't bother you, don't bother it.
Trustworthy means that a software product or component is safe, reliable and secure. Checklist for Software Design for Reliability 1. Simplify 2. Use fault tolerant libraries and transfers for recovery. 3. Rejuvenate the executing system from time-to-time. 4. Hire good people and keep them! 5. Limit programming features. 6. Limit module size initialize memory. 7. Check design stability. 8. Bound the execution domain. 9. Engineer to performance budgets. 10. Reduce algorithm complexity. 11. Factor and Re-factor. 12. Improve maintainability [with 20% of staff].
IEEE DVP talk
