4 ms·
An old friend, so many postings, so little discussion. Given the usual high standard of discussion here on HN, it's a shame that there's been so little about t
by ColinWright 13y ago
An old friend, so many postings, so little discussion. Given the usual high standard of discussion here on HN, it's a shame that there's been so little about this popular submission. FWIW, I've upvoted this, because I really do want to see a balanced discussion about it from an up-to-date viewpoint.
It was the Turing Award Lecture in 1972 - it's over 40 years old. Printed in "Classics in Software Engineering" by Yourdon Press, 1979, ISBN 0917072146.
HTML: http://www.cs.utexas.edu/~EWD/transcriptions/EWD03xx/EWD340.html http://www.cs.utexas.edu/~EWD/transcriptions/EWD03xx/EWD340....
PDF: http://www.cs.utexas.edu/~EWD/ewd03xx/EWD340.PDF http://www.cs.utexas.edu/~EWD/ewd03xx/EWD340.PDF
Here are some of the previous submissions here on HN:
https://news.ycombinator.com/item?id=86288 https://news.ycombinator.com/item?id=86288
https://news.ycombinator.com/item?id=109724 https://news.ycombinator.com/item?id=109724
https://news.ycombinator.com/item?id=126638 https://news.ycombinator.com/item?id=126638
https://news.ycombinator.com/item?id=135111 https://news.ycombinator.com/item?id=135111
https://news.ycombinator.com/item?id=156505 https://news.ycombinator.com/item?id=156505
https://news.ycombinator.com/item?id=449806 https://news.ycombinator.com/item?id=449806
https://news.ycombinator.com/item?id=1179277 https://news.ycombinator.com/item?id=1179277
https://news.ycombinator.com/item?id=1649246 https://news.ycombinator.com/item?id=1649246
https://news.ycombinator.com/item?id=1672262 https://news.ycombinator.com/item?id=1672262
https://news.ycombinator.com/item?id=1799296 https://news.ycombinator.com/item?id=1799296 <- 3 comments
https://news.ycombinator.com/item?id=1894784 https://news.ycombinator.com/item?id=1894784 <- 8 comments
https://news.ycombinator.com/item?id=2011732 https://news.ycombinator.com/item?id=2011732
https://news.ycombinator.com/item?id=3060828 https://news.ycombinator.com/item?id=3060828
https://news.ycombinator.com/item?id=5035560 https://news.ycombinator.com/item?id=5035560
https://news.ycombinator.com/item?id=5266220 https://news.ycombinator.com/item?id=5266220
https://news.ycombinator.com/item?id=6112467 https://news.ycombinator.com/item?id=6112467 (This item)
- pavs 13y agoI dunno about others, but I am a slow reader, and this will probably take me about 20 minutes to finish reading. I have a general rule on sites like HN and Reddit, if it takes more than 10 minutes to read something I will probably not going to read it (unless it's extremely interesting, important or relevant to present time based on comments). I spend about an hour on HN a day, in small bouts. Most of the time I will skim over titles to see if there is anything interesting, if there is and its a long read (like this one) I will save it to "Pocket" to read it later. I will probably get around to reading this few weeks or even a month from now. I suspect, very few people will read it on the spot, which is why even interesting submissions like this doesn't get a lot of discussions.
- prawks 13y agoDitto. This sounds like a great article, but it looks immensely dense. It's most definitely on my "To-read" list, but that rarely gets actually read through... Also, although the author carries immense weight, and I'm sure the ideas put forth in the article are fantastic, what benefit will I get out of the article other than "hmmm, well that was interesting"? It's not a tutorial on a tool I can put into practice, or necessarily any sort of technique I can use in my day-to-day life (at least before reading, it seems this way). It looks like a philosophical article about the art of programming and being a programmer. I love these kinds of articles, but their return on the large time investment required is ultimately not very large. This is in my relatively limited experience, of course.
- chaddeshon 13y agoThese are two of the most depressing comment I've ever read, not just on Hackernews, but on the whole internet. So much so that I wonder if they were written with sarcasm that escapes me. They represent a philosophy that is referenced often but always before as an unintentional consequence of our internal laziness -- a laziness that should be fought against. However here it is being presented as a conscious choice. Indeed a right, proper, and good, choice. The commenters seem to be arguing that reading is only worth the time if the content has been distilled to its basic facts, and further that that facts need to be immediately actionable. Have we no room for soul? Do we lack the energy to take general concepts and apply them to new areas in new ways? When we break a larger writing down and extract just the main theses, we make it easier and quicker to under understand, but we also neuter and even change the meaning. Sometimes what we learn or what we experience is subtle. Sometimes writing doesn't give us a todo list, but instead it ever-so-gently shades and nudges all our todo lists.
- pavs 13y ago> The commenters seem to be arguing that reading is only worth the time if the content has been distilled to its basic facts, and further that that facts need to be immediately actionable. Have we no room for soul? Do we lack the energy to take general concepts and apply them to new areas in new ways? You are reading too much into it. I (and probably the person you replied to) have nothing against long-form articles, as a matter of fact I prefer them. On a typical day, I will spend 1-2 hours on a book, I will read many smaller articles here on HN and on Reddit, I will also check out my RSS reader, I will read work-related email, I will do actual work, I will train for my marathon (alternate day running and weights) which takes about 2 hours, spend time with my family, socialize, and hopefully get some sleep too. Its all about how you manage your time, not about distilling long-forms into bite-size chunks. If given a choice between reading a long-form article online or reading a book, I will read a book. There is only so much time in a day. There is so much to do. I save long article like this for my lazy or slow days to read.
- LekkoscPiwa 13y agomaybe HN is not what you are taking it for?
- stiff 13y agoMaybe it is so because this is a very wordy article with Dijkstra having just his usual axes to grind? The debate about this article should be a debate about the merits of proving program correctness, even though people nowadays read in Dijkstra many other things he probably did not even mean; anyway, this debate has been done to death in the period when there was still any controversy about using it as a technique for day-to-day programming. I think the problem with Dijkstra is that A) he views every program as a huge algorithm, where 90% of programming now is doing IO and user interfaces B) he doesn't take into consideration that people can have different brain wiring than he has and be effective with other techniques that the ones he advocates.
- smoyer 13y agoI reread this piece every few years and agree that there's no reason this discussion can't occur every few months/years on HN (so I'm upvoting this too). And since there's a lack of comments on many of the threads, I'll add my opinion to this one. This was written by a man who's got a long-term love affair with programming. I recognize this because I am the same way, and it's actually rarer than you might think. Most of the people who were my colleagues have gone on to management, or more likely switched to other careers. I've been in management repeatedly (even C-level) and have had to talk my way back into software architecture and development. I wrote my first program 41 years ago and it's still my favorite past-time.
- davidp 13y agoIt's indeed a classic. I think one reason why there's relatively little discussion is that in the intervening years Dijkstra has been proven so correct that there's relatively little to say. But I suspect that the main reason why it's hard for most people to talk about his work is that they lack the historical context to understand what he's talking about. For someone who has never studied or used FORTRAN, ALGOL 60, or any of the macro languages he alludes to, his criticisms seem very abstract. For someone who has seen those languages, they're concrete and visceral. Looking back twenty years ago, I now understand that one of the highest-value courses in my CS degree was the "Survey of Programming Languages" class. We spent two to three weeks studying and working with each of LISP, FORTRAN, ALGOL-60, Smalltalk, and a couple others I don't remember. I enjoyed the class but at the time I wasn't developed enough to think more than "man, people sure have come up with some strange ways of doing things; ok, back to C, I love my filesystems class." Now I recognize how precious that exposure was. It's kind of like traveling; exposure to different cultures teaches you as much about your own culture as about theirs. You don't always realize what assumptions you're making until you see other people making different assumptions. This is the value of formal CS education, i.e. Dijkstra's life work. Some people ask whether a CS degree is worthwhile when the Internet makes it so easy to learn how to program. It's the difference between university and vocational training; if you only want fix cars, you just need some skills classes and time spent apprenticing in a mechanic's shop. If you want to be an automotive engineer, you need an engineering education. If you just want a job, you don't need college; if you want to participate in the core of what our civilization has to offer, you need an education (self-study or formal, doesn't matter). (Tip for the kids in school today: If you're at university and you find yourself frequently saying "Why do I have to learn this crap? I'll never use it!" then you might just be wasting your time and money. Do yourself a favor and drop out, unless someone else is paying for your play time. But if you learn for the sake of learning, if you recognize that learning how to learn, to prepare for a lifetime of learning, is the point of education, then stay in school, since you'll reap the rewards many times over.)
- lesterbuck 13y agoA recent version of programming languages survey class available to anyone is the Coursera class on Programming Langauges from Dan Grossman: https://www.coursera.org/course/proglang https://www.coursera.org/course/proglang It will be taught again in the fall. He covers three languages (SML, Racket, and Ruby) in ten weeks, hitting three of the four quadrants on strongly typed/dynamic and functional/object oriented.
- mratzloff 13y agoAny content aggregator where stories float to the top but are increasingly depressed according to the passage of time suffers from this. Articles requiring a few minutes are ideal, while longform essays are usually marked for later reading. By the time someone has a comment, the thread is buried under mountains of short, easily-digestible "Reasons I Like Go" and "New MySQL Vulnerability"-type posts.
- mjn 13y ago> Printed in "Classics in Software Engineering" by Yourdon Press, 1979 It's interesting how terminology has changed. In the 1970s you might have been able to say that Dijkstra was part of a field called "software engineering", in that he was writing about methodology for developing software. But in the 1980s it became a fairly different field, focused more on how to develop effective processes for large-scale development (modeling, testing, code review, team structure, tooling, etc.). By 1988 Dijkstra was vehemently against that version of software engineering. Here's his article on that subject: http://www.cs.utexas.edu/~EWD/transcriptions/EWD10xx/EWD1036.html http://www.cs.utexas.edu/~EWD/transcriptions/EWD10xx/EWD1036... A number of these phenomena have been bundled under the name "Software Engineering". As economics is known as "The Miserable Science", software engineering should be known as "The Doomed Discipline", doomed because it cannot even approach its goal since its goal is self-contradictory. Software engineering, of course, presents itself as another worthy cause, but that is eyewash: if you carefully read its literature and analyse what its devotees actually do, you will discover that software engineering has accepted as its charter "How to program if you cannot.".