Comments on: Quality Flow http://www.nomadicminds.org/jnpr/2008/10/quality-flow/ The views expressed here are my personal opinions, have not been reviewed or authorized by Juniper Networks and do not necessarily represent the views of Juniper Networks. Sat, 13 Mar 2010 20:33:05 +0000 http://wordpress.org/?v=2.6 By: Loud Thoughts » Blog Archive » Quality Flow http://www.nomadicminds.org/jnpr/2008/10/quality-flow/#comment-35 Loud Thoughts » Blog Archive » Quality Flow Sun, 02 Nov 2008 03:24:05 +0000 http://www.nomadicminds.org/jnpr/?p=88#comment-35 [...] What separate professional software development and amateur? The ratio of effort devoted on quality. Amateurs make it work. Professional show evidences. The amount of efforts in professional software houses devoted to quality and verification easily dwarfs standard definition of development effort.’ Read more… [...] [...] What separate professional software development and amateur? The ratio of effort devoted on quality. Amateurs make it work. Professional show evidences. The amount of efforts in professional software houses devoted to quality and verification easily dwarfs standard definition of development effort.’ Read more… [...]

]]> By: gwynne stoddart http://www.nomadicminds.org/jnpr/2008/10/quality-flow/#comment-31 gwynne stoddart Sun, 19 Oct 2008 17:31:13 +0000 http://www.nomadicminds.org/jnpr/?p=88#comment-31 May I offer an observation.... there's a gem at the beginning...people actually spending quality time *looking* at code...rather than the indirect effects of the code... "The verification takes place in phases. First is the effort to make sure the software works as designed. This is most commonly done by the same person who designs the software, but more effective if by someone who sits close to him/her and watches over his/her shoulders as he/she codes. The goal is to make sure the software behaves well for all ranges of inputs." May I offer an observation…. there’s a gem at the
beginning…people actually spending quality time *looking* at code…rather than the indirect effects of the code…

“The verification takes place in phases. First is the effort to make
sure the software works as designed. This is most commonly done by the
same person who designs the software, but more effective if by someone
who sits close to him/her and watches over his/her shoulders as he/she
codes. The goal is to make sure the software behaves well for all
ranges of inputs.”

]]>