Criar um Site Grátis Fantástico


Total de visitas: 53772
A discipline of programming pdf download

A discipline of programming by Edsger W. Dijkstra

A discipline of programming



Download eBook




A discipline of programming Edsger W. Dijkstra ebook
Publisher: Prentice Hall, Inc.
ISBN: 013215871X, 9780132158718
Page: 232
Format: djvu


It matters because ultimately writing code is about discipline and details. Great programming is a 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. The short answer is an emphatic 'yes'. IMHO, the closer you are to the money, the more you make. Knowing that the details make the product itself. Unknown November 13, 2011 at 10:29 AM. The most common excuse is that "a cluttered desk is a sign of a brilliant mind. Their desks are often littered with stacks of paper and other debris. As a result Alistair sees Crystal as requiring less discipline than extreme programming, trading off less efficiency for a greater habitability and reduced chances of failure. Mature aspect-oriented frameworks offer a disciplined approach to programming. If DH were an accepted discipline, the recognition of programming activities or contributions to databases as scholarly accomplishment would not be such a big deal. What I write about computer programming applies to other fields of problem solving, such as engineering and mathematics. That's not accidental — I think that, even in as fast-moving a discipline as programming, it takes time for a book to establish itself as a classic; and the really good books are timeless. It is well known that programmers generally abhor organization and discipline. 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. Does it really matter what the code looks like? To Ander's defense, let me acknowledge that AspectJ has been used for the ugly. The sole justification for discipline in software development and maintenance, is that it as it prevents defects. I've done both and I think it is unfair.