Subroutine Quotes

Constructs extraneous to the real world should be eliminated from the analysis model. They may be needed later during design, but not now. For example, CPU subroutine, process, algorithm, and interrupt are implementation constructs for most applications [and should be excluded from the analysis model]... (James Rumbaugh)
Ritchie and Thompson made an amazing team; and they played Unix and C like a fine instrument. They sometimes divided up work almost on a subroutine-by-subroutine basis with such rapport that it almost seemed like the work of a single person. In fact, as Dennis has recounted, they once got their signals crossed and both wrote the same subroutine. The two versions did not merely compute the same result, they did it with identical source code! Their output was prodigious. Once I counted how much production code they had written in the preceding year − 100,000 lines! Prodigious didn't mean slapdash. Ken and Dennis have unerring design sense. They write code that works, code that can be read, code that can evolve. View quote
Doug McIlroy
Sometimes at night I worry about TAMMY. I worry that she might get tired of it all. Tired of running at sixty-six terahertz, tired of all those processing cycles, every second of every hour of every day. I worry that one of these cycles she might just halt her own subroutine and commit software suicide. And then I would have to do an error report, and I don't know how I would even begin to explain that to Microsoft. View quote
Charles Yu
Astonishingly, in spite of decades of research, there is no agreed theory of cancer, no explanation for why, inside almost all healthy cells, there lurks a highly efficient cancer subroutine that can be activated by a variety of agents - radiation, chemicals, inflammation and infection. View quote
Paul Davies