Toward zero-defect programming
by Allan M. Stavely · first published 1999
3mentions
1recommended by
3HN commenters
2018–2023first – last mentioned
33% recommend67% neutral
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
…user acceptance is quite common and recommended. Pick a prototyping language unsuitable for production ;) That way prototypes can't "accidentally" be turned into production software. Consider reading "Toward Zero-Defect Programming" (1st Edition) by Allan M. Stavely.
on “Design via Proposed Documentation” ↗…concrete examples I like that you're all doing that. That does help a lot. I plan to do my part to some degree in the near-ish future: I bought the High-Integrity Applications book for SPARK and Stavely's Toward Zero-Defect Programming for Cleanroom. http://infohost.nmt.edu/~al/cseet-paper.html SPARK book looks well-written but kind of packed with info esp on the language. Might take some time for me to learn. The Cleanroom book is…
on “Mathematics for Computer Science: Readings” ↗…experienced such a nice development process. Nowadays I have to consult five coworkers to ask how to call their undocumented methods and initialize the classes. I have recently encountered the book 'Toward Zero-defect Programming', where exactly this approach is recommended. Key points are (from the top of my head): 1. You should know the programming language you're using inside-out. 2. Don't *try* your code, but *reason*…
on “It Can Be Done (2003)” ↗