A discipline of programming Edsger W. Dijkstra
Publisher: Prentice Hall, Inc.
But as Daylight argues in this fascinating historical account of the development of computer programming as a discipline in the 1950s and 60s, the real story is much more complicated. Thus the discipline of programming has become blurred. Dijkstra made a similar argument on page 56 of his book "A Discipline of Programming", together with another argument in support of the != form. With a few notable exceptions (e.g. Programming is a discipline, a discipline that is often undermined and taken lightly. Perhaps a step back in In Problem Seeking , the classic quote and discipline separation was stated as "Programming is problem seeing, design is problem solving. However, accessibility is only part of the story. Murnane, 1993) most research about the cognitive effects of computer programming seemed to have focused on programming as a problem solving rather than a linguistic activity. The reaction of these teams suggested their levels of discipline with various practices. Alexander's mathematical concepts and orientation were similar to Edsger Dijkstra's influential A Discipline of Programming. We might talk about reaching as wide an audience as possible, or about laws requiring accessible websites. If computer languages were To write a decent program, you have to discipline your brain *far* more than you would need with any language (because, let's face it, other people are forgiving but compilers or computers are not). Abstract for Haskellers: This is a long, involved defense of purity, both in terms of what it affords us in terms of power and in how it enforces “good” programming practices. Van Wijngaarden, persuaded him that in the years to come he could be one of the people to make programming a respectable discipline. For a long time I thought that Dijkstra's 1976 book “A Discipline of Programming” was a preview of the promised land by showing how to do this, not with assertions, but with guarded commands and weakest preconditions.