A discipline of programming Edsger W. Dijkstra
Publisher: Prentice Hall, Inc.

Programming is a discipline, a discipline that is often undermined and taken lightly. 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). According to Dijkstra's experience, described in chapter "The problem of next permutation" of "A Discipline of Programming", the separation of code and data is essential for clarity. I think for some reason computer programming is often miscategorized as a discipline to study or a class to take that's only relevant for aspiring software engineers. If you take a look at his “A Discipline of Programming” (which is admittedly not an easy sit for the general reader) you'll understand he's talking about “correct-by-construction” programming. A discipline like Extreme Programming requires a radical upgrade in both technical and social skills, especially for programmers. Dijkstra talks about this problem in detail in one of my favorite books, "A discipline of programming." Also, here's an article with a surprisingly simple recursive solution: http://nicolas-lara.blogspot.com/2009/01/permutations. So I've been doing TDD with one project, and LP with another project, and I've come to a rather amusing conclusion: Test Driven Development and Literate Programming are the same discipline. It requires become transparent, accountable, and responsible. Somewhere in the middle are the true software engineers, who approach computer programming in a disciplined and rigourous knowledge-based manner, similar to that of engineers in other fields. 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. With a few notable exceptions (e.g. Dijkstra, A Discipline of Programming, * Prentice-Hall, 3.