And a guy who is famous both for being incredibly clever and for being rather arrogant and insecure told all his competitors that they were incompetent if they didn't do it the hard way.
Programming is a form of mathematics. Maths papers are terse and beautiful and look as though they have sprung fully armed from the head of Zeus.
But you don't see the days of hacking through examples and crazy leaps of intuition (that are almost always wrong) in the finished paper, because the mathematician removes them from the story in order to leave an argument that is easy to verify.
I am not saying that Dijkstra couldn't do things the hard way. I would be amazed if his best stuff was done the hard way.
Lakatos in his "Proofs and Refutations" addresses precisely this topic.
Even Alonzo Church published work that was later shown to be logically inconsistent http://en.wikipedia.org/wiki/Lambda_calculus I came across
You'd be surprised at how doable that is if you actually tried. It's the same as every other problem in programming: break it down in to two pieces, figure out which one is the easier, if it is trivial solve it, otherwise recurse.
You'd need an overall sketch of the architecture before you began but once you have that worked out it's 'just programming' to get you to the finish line.
The hardest part to get right is security, especially if you go multi-user, but since you just specify 'multitasking operating system' that one is somewhat limited in scope.
(such thinking probably gave us windows ;) )...
Easier to not inject a bug in the first place than to try to find it later.
It can be a slow process with less 'instant gratification' than web programming.
This was before the age of virtual machines on PCs. Getting it to become self hosting took about 6 months or so.
It is compared to QEMU :)
Why wasn't I doing that already? I'd been reading too much Dijkstra, that the "competent" programmer can show whether his code will work or not. It's definitely possible to do it that way, but it's (very sadly) too high a standard for me to reach in reasonable time (or maybe at all), for more than toy problems. Dijkstra used this approach to write a multitasking operating system. I'm pretty sure I couldn't do that.