The unbelievable thing is that this machine is now being advertised with the "wonderful operating system" that relieves the programmer of so many tasks! This glosses over the facts that:In (*), he criticizes that the programs have to address memory instead of information, which dumps the responsibility of memory management to the programmer.
- a large part of these tasks are necessitated by the hardware and would have been easier or non-existent in a better design; (*)
- this operating system implies an alarming overhead (but IBM is happy to supply a faster model from the family);
- the tasks have not been obviated, but have been transferred to the computing centre's management, which has to dimension and manage the machine
- the creation of this operating system turned out to be a programming task beyond the capabilities of the manufacturer; (**)
- that the system has become such a baroque monstrosity that no user can venture to adapt it.
About (**), Dijkstra comments in EWD1303 that when the OS turned out to never be properly completed he wasn’t surprised:
In order to make errors reproducible they equipped the IBM/360 with a special hardware monitor; in the recording mode it would capture precisely where in the computation each interrupt took place, in the controlling mode it would force the computer to replay exactly the recorded computation, thus making intermediate results available for inspection. It struck me as a crude and silly way of proceeding, and I remember being grateful that lack of money had protected me from making that methodological mistake. I felt grateful and superior, and when a few years later it became clear that IBM couldn’t get its OS/360 right, I was not amazed.He is dissing as a “methodological mistake” what even now would be considered a pretty good debugger! So, according to Dijkstra, we are pretty much living in hell. I would love to know what they had by then. SICP says early on that Computer Sciences do not study the computer, in the same way that Astronomy does not study the telescope. Maybe we have really started looking at the hand and missed the moon? But back to Brooks: in 1986 he wrote No Silver Bullet, where the main recommendations are:
- Buy software, do not build it; in particular, given cheap SW, people will adjust to it, instead of wanting to adjust the SW. So he recommends providing users with a generic word processor, spreadsheet and drawing program so they are pretty much self-suficient for anything (instead of building special tools for each company). Cue MS Office.
- Customer does not know, can not know what s/he wants. So he recommends fast turnaround, fast iterative development: cue the Agile movement
- He talks about using OOP to remove "accidental difficulty" from the process, “allowing the designer to express the essence of the design without having to express large amounts of syntactic material that add no information content”…
…but he stops at OOP? Makes me think that he was not very informed about functional programming, given that OOP is (1) trivial to add to functional programming languages, (2) dissed by all the greats as uninteresting – or worse.
Interestingly, on 1987 the second AI winter started.
…well over half of the time you spend working on a project (on the order of 70 percent) is spent thinking, and no tool, no matter how advanced, can think for you. Consequently, even if a tool did everything except the thinking for you – if it wrote 100 percent of the code, wrote 100 percent of the documentation, did 100 percent of the testing, burned the CD-ROMs, put them in boxes, and mailed them to your customers – the best you could hope for would be a 30 percent improvement in productivity. In order to do better than that, you have to change the way you think.70% of the time thinking – but, how much of that time is spent breaking down the ideas into small-enough morsels that can be fed to the computer? That is, how much time is spent being what Paul Graham calls "the human compiler"? Wouldn't that be fixed by using higher-level languages? In this same direction, Brooks writes something that doesn't stand to scrutiny:
The complexity of software is an essential property, not an accidental oneThat's in fact like throwing your hands up and admitting defeat. But that complexity is much finer grained, and the distinctions have a big influence in the whole process. A trivial example: in 2010 I had to write a piece of software using Borland C++ – an IDE and environment from about 1998. The IDE itself had a crap help system, the libraries included too, and the net was practically devoid of any information or possibilities of help about it all; add to that the extra bugs coming from using the still-barely-Windows 95 IDE, and its products, on a Windows XP. Of course I WOULD have used any number of free, current-day systems instead of that IDE. But I HAD to use it. And that mandate made a lot of things take around twice the time and effort they should have taken. That is an extreme example of forced complexity, yes; it's extreme just to drive the point home clearly. But we are so used to milder examples of arbitrary complexity that I believe that we are swimming in a sea of such forced complexity.
For example… Do you already use restricted pointers in your C code?Or… Are you at least familiar with the strict aliasing rules that are in place since C99? You know, 16 years ago; the rules that gcc enforces for you if you are using C99 or C11 and optimization, even though probably it won't warn you when you break them – and instead will happily generate Undefined Behaviour. Oh, and did you know that GCC 5 by default enables C11, instead of the C89 that was used up to GCC 4.x? This transition will be a good moment to realize the hike in complexity. But surely soon we'll get used to it, and the peak will drown in the normal noise level. Because, hey, it's only natural that the compiler needs help from the "human compiler" to optimize things, right?
A great post on Brooks vs Functional: http://paulspontifications.blogspot.com/2007/08/no-silver-bullet-and-functional.htmlAnd a bit (well, much more than a bit) of OOP bashing:
UPDATE: another paper from 2006, "Out of the tar pit", deals with the subject of "No Silver Bullet" vs functional (and other) programming, and makes a far more convincing point than I could – while delving on functional and logic programming (and more!), and how they can fix things.