5 ms·

I agree with Dijkstra, the looping constructs of FORTRAN's DO and ALGOL 60 were too baroque. Dijkstra's comments were written in 1977, at that time FORTRAN IV a

by todd8 10y ago

I agree with Dijkstra, the looping constructs of FORTRAN's DO and ALGOL 60 were too baroque. Dijkstra's comments were written in 1977, at that time FORTRAN IV and ALGOL 60's loop semantics were a mess and were common sources of errors. Without qualification, Dijkstra was one of the greatest computer scientists in our field's short history. While I don't agree with every single one of his ideas, I would encourage budding computer scientists and professional programmers to look over what he accomplished. He most certainly was not unproductive. Wikipedia says that Dijkstra is known for: - Dijkstra's algorithm (single-source shortest path problem) - DJP algorithm (minimum spanning tree problem) - First implementation of ALGOL 60 compiler - Structured analysis - Structured programming - Semaphore - Layered approach to operating system design - T.H.E. multiprogramming system (one of the first operating systems) - Concept of levels of abstraction - Concept of layered structure in software architecture (layered architecture) - Concept of cooperating sequential processes - Concept of program families - Multithreaded programming - Concurrent programming - Concurrent algorithms - Principles of distributed computing - Distributed algorithms - Synchronization primitive - Mutual exclusion - Critical section - Generalization of Dekker's algorithm - Tri-color marking algorithm - Call stack - Fault-tolerant systems - Self-stabilizing distributed systems - Resource starvation - Deadly embrace - Deadlock prevention algorithms - Shunting-yard algorithm - Banker's algorithm - Dining philosophers problem - Sleeping barber problem - Producer–consumer problem (bounded buffer problem) - Dutch national flag problem - Predicate transformer semantics - Guarded Command Language - Weakest precondition calculus - Unbounded nondeterminism - Dijkstra-Scholten algorithm - Smoothsort - Separation of concerns - Program verification - Program derivation - Software crisis - Software architecture This quote by galactipony is really offensive to me: > Such people, while very smart, make for very unproductive software engineers. They also have a way of sounding deceptively smart and thoughtful, when really they're just talking out of their ass. Beware. It is quite clear to me that Dijkstra wasn't "just talking out of [his] ass." Learn more about Dijkstra at https://en.wikipedia.org/wiki/Edsger_W._Dijkstra https://en.wikipedia.org/wiki/Edsger_W._Dijkstra or in any resource on the history of Computer Science.

galacticpony 10y ago
I know about Dijkstra. I didn't say Dijkstra was talking out of his ass in this case. I'm saying you often can't tell when people like him are talking out of their ass, as they sometimes do. Who would think the inventor of all these algorithms would ever utter a half-formed thought, on a whim? Unthinkable! Yeah... no. Another distinction you fail to see is that somebody who is great at finding the best or optimal algorithms (i.e. a great theorist) isn't necessarily a productive programmer. To the contrary, perfectionism and productivity are at great odds. Dijkstra was heavily at odds with real-world programming as it was done, to the point of isolating himself with his work. If we followed his opinions on how to program, we wouldn't get much of anything done.
- throwaway729 10y ago
  > Another distinction you fail to see is that somebody who is great at finding the best or optimal algorithms (i.e. a great theorist) isn't necessarily a productive programmer. I suppose what you're saying here is that there are a lot of business tasks which don't require a great theorist. I don't think Dijkstra would disagree. But still, calling Dijkstra an "unproductive programmer"? Really? I'll take one Dijkstra's algorithm over a dozen web apps. And if I can have a patent on it, I can even make a solid business case for that choice. > If we followed his opinions on how to program, we wouldn't get much of anything done. And yet, how many man-years of engineering effort could we waste having bad theorists who can quickly hack out LoB code try to re-invent Dijkstra's algorithm? Perhaps software engineering is a very wide field, and it takes all types?
- importantbrian 10y ago
  > To the contrary, perfectionism and productivity are at great odds. I've learned this the hard way in my career. I always have to fight against taking the extra 20 hours to perfect something when it only took me 1 hour to get to 95% and 95% is more than good enough for the particular task.

by todd8 10y ago

galacticpony 10y ago

I know about Dijkstra. I didn't say Dijkstra was talking out of his ass in this case. I'm saying you often can't tell when people like him are talking out of their ass, as they sometimes do. Who would think the inventor of all these algorithms would ever utter a half-formed thought, on a whim? Unthinkable! Yeah... no. Another distinction you fail to see is that somebody who is great at finding the best or optimal algorithms (i.e. a great theorist) isn't necessarily a productive programmer. To the contrary, perfectionism and productivity are at great odds. Dijkstra was heavily at odds with real-world programming as it was done, to the point of isolating himself with his work. If we followed his opinions on how to program, we wouldn't get much of anything done.

throwaway729 10y ago
> Another distinction you fail to see is that somebody who is great at finding the best or optimal algorithms (i.e. a great theorist) isn't necessarily a productive programmer. I suppose what you're saying here is that there are a lot of business tasks which don't require a great theorist. I don't think Dijkstra would disagree. But still, calling Dijkstra an "unproductive programmer"? Really? I'll take one Dijkstra's algorithm over a dozen web apps. And if I can have a patent on it, I can even make a solid business case for that choice. > If we followed his opinions on how to program, we wouldn't get much of anything done. And yet, how many man-years of engineering effort could we waste having bad theorists who can quickly hack out LoB code try to re-invent Dijkstra's algorithm? Perhaps software engineering is a very wide field, and it takes all types?
importantbrian 10y ago
> To the contrary, perfectionism and productivity are at great odds. I've learned this the hard way in my career. I always have to fight against taking the extra 20 hours to perfect something when it only took me 1 hour to get to 95% and 95% is more than good enough for the particular task.