Those who want really reliable software will discover [authority!] that they must find means of avoiding the majority of bugs to start with [unsubstantiated!], and as a result the programming process will become cheaper [unsubstantiated!]. If you want more effective programmers, you will discover [authority!] that they should not waste their time debugging [repeated assertion!], they should not introduce the bugs to start with [repeated assertion!].
He could just say:
When creating reliable software debugging takes up much time. If we develop techniques that prevent these bugs from being introduced in the first place then programmers will become much more effective.
Good writing is terse and easy to understand. It should lead the reader from the premises to the conclusions. Good writing shouldn't contain pretentious detours. I don't think you should emulate Dijkstra.
You might argue this is improper, but I think that's a bit morose. I dread the day when all people write like that second sentence.
That's not to say someone should emulate him, though. It's not that it's wrong, it's that they're bound to fail and produce something tinny and derivative. That's the thing your revised sentence has going for it: it's as cheap as it is limp.
If something becomes boring and derivative when stated plainly then there was nothing of substance to start with.
> Good writing is terse and easy to understand.
Good writing does what it sets out to do. "terse and easy to understand" is a fantastic style for certain objectives, but there's no one "good writing" style.I think you might be blurring the lines between writing something in a socratic dialogue versus writing technical documentation. Dijkstra, obviously often is writing in the former style and so there's plenty of room for his personality in the text and it doesn't take away from the overall quality and cohesiveness of the text.
I also don't mind unsubstantiated claims. It's just obnoxious to phrase it like "any person with half a brain knows [controversial claim]".
This bugs me as well. He's obviously made profound and exceptional contributions to the field but I don't like when he writes in the manner you pointed out where he's making bold statements without evidence. Worse is when people quote something Dijkstra wrote that he didn't back up with evidence as if it's true just because Dijkstra wrote it.
Reciting your writing out loud helps too. If it isn't in the desired tone and/or it doesn't sound natural, rewrite it. You may find you need less adverbs than you think.
Books on writing style and techniques help in the way books about algorithms, paradigms, design patterns and other facets of programming help. The key is to implement the ideas you learn in your writing.
There were of course a lot of things of smaller scope to be done, and the unification of EM and the weak nuclear force was in the future, as well as the imperfect Standard Model that adds the strong nuclear force, and we still haven't unified gravity and the other three fundamental forces, but programming was wide open, and what you could do was rapidly improving as the machines were rapidly becoming faster and bigger. ADDED: For example, the Electrologica X1 he did his Ph.D. thesis on was solid state, as in completely transistorized (no vacuum tubes) and had magnetic core memory, both major advances in the '50s.
Heck, my calling was science, and I was strongly on that track as of 1968, but computers nonetheless gained a lot of my attention starting in the mid-late '70s, as they did for Feynman starting with the Manhattan Project when "computers" were the operators of 10 digit electromechanical scientific calculators.
Practice makes perfect, that's really all there is to it. A good book on writing style can help, but only if you use it. The Sense of Style by Steven Pinker and Revising Prose by Richard Lanham are my two favorites.
Similarly for public speaking, practice makes perfect. Check out Toastmasters International - a nonprofit that is running clubs all over the world where members can improve their public speaking skills in a supportive environment. Worked for me.
I'd like to point out that Dijkstra's writing might arguably the best writing I've seen from a programmer. English is not my first language and his writing is inspiring; if possible I'd like to request if anyone can point me to a resource (apps, software, etc) so I can learn to write, speak, and converse like Dijkstra in this lecture?