unfortunate word choice, I think, since process is sort of the point of the whole affair. Not in the sense you meant it there, of course, but in the more genera

unfortunate word choice, I think, since process is sort of the point of the whole affair. Not in the sense you meant it there, of course, but in the more general sense of formalizing "how to", from developing adequate descriptions of what - data structures and so forth - to finding the best ways of getting from point a to point b (or finding out that there isn't one and looking for a good-enough good-enough). It's almost a shame that computer and electronic computer are nearly synonymous now; it leads to the idea that CS is somehow a science about these electronic computing machines rather than about computing itself. While it's true that advances in CS have implications for the machines and the way we use them, that's almost incidental to the task of finding the best ways to describe, express and carry out a process. And if it turns out that a (seemingly) ridiculous amount of time is spent at the beginning demonstrating that adding in a place system is usually better than counting, and multiplying is better than adding the same number a whole bunch of times, well, if all you've gotten from that is that typing "*" saves you a few keystrokes, then you've missed the point.