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.