06-28-2007 09:44 AM
06-28-2007 09:52 AM
06-28-2007 09:56 AM - edited 06-28-2007 09:56 AM
Message Edited by mikeporter on 06-28-2007 10:57 AM
06-28-2007 12:43 PM
@mikeporter wrote:
A couple years ago they published a collection of Parnas' papers called modestly: "Software Fundamentals". As I travel around the country working there are very few books I schlep around with me - this is one of them. His paper on Modular Decomposition (from 1972!) is a well you can go back to again, again and again...
06-28-2007 12:45 PM
Joe,
@JoeLabView wrote:
somehow... something seems to be missing wrt "design".. there has to be an element of design in there..
06-28-2007 12:50 PM - edited 06-28-2007 12:50 PM
@gchristi1 wrote:
I clicked on mikeporter's link and like the David Parnas quote:
"Software Engineering - an unconsummated marriage"
Message Edited by Jim Kring on 06-28-2007 10:51 AM
06-28-2007 01:31 PM
06-28-2007 01:45 PM
@mikeporter wrote:
One thing I will always remember is many years ago sitting reading a paper he wrote in (I think) 1968 and trying to figure out how it would apply to LV development in 1987. At one point he made the statement to the effect of:
"...imagine that your subroutines all have front panels with knobs and switches..."
I remember thinking: "Hot damn! My subroutines do have front panels - with knobs and switches!" I really need to look up that reference. It would make a great sig.
Mike...
06-28-2007 06:18 PM
🙂
Three Things I Learned About Software in College
2.) Software engineering is the art of amassing collected anecdotes and calling them Best Practices when in truth they have more in common with fads than anything else.