Reply to thread

Message: [QUOTE="Phlip, post: 3857365"] You mean besides Robert C. Martin teaching TDD at Boeing? [URL]http://www.fastcompany.com/magazine/06/writestuff.html[/URL] The equivalent steps are... - every code change reviewed during the change (review of static code, post-change is less important) - logging every change & every bug - both white and black box tests - running the build environment & all tests after every edit - collecting requirements in realtime... Put another way, if you took that process and then streamlined out the excesses (pseudocode, multiple teams, multiple redundancies, strict type checking, automated proofs, etc.), you would have competitive commercial software development with a low bug rate. [URL]http://www.google.com/search?q=standish+group+software+chaos[/URL] [/QUOTE]