The psychology of program computing
Someone really ought to study the psychological effects of giving a faster computer to a programmer. The effects don't last long, but I'm sure that for a while it makes you significantly more productive. I recently upgraded my workstation to (approximately) three times faster machine, and, wow, what a difference it makes. Suddenly compiling Java classes, the set of few that usually are changed at a time, drops from couple of seconds to a blink of an eye, so to speak. All seems so easy; bugs can be squashed and features added.
This all is because I have had switched to Eclipse as my primary, the only, Java development environment, and while I don't mean to complain; that is, I'm OK with it, Eclipse really is rather resource-hog. I quite like code completion, but if it takes several seconds to do the completion, it really begins to annoy. It's perfectly OK to wait longer for a larger build to finish, but sluggishness in text editing is very irritating.
[permalink] [2 comments] 06.08.2004, 23:03
- Comments:
Posted by Mark Eichin at 08.08.2004, 06:15
I read somewhere (Raskin probably has confirmation of it, but my initial reference was much older) that anything over 100milliseconds isn't "interactive" - and that as long as you can get the reaction down below that threshhold, you don't actually need to make it much faster, but the threshhold is critical. Thus, your frustration is quantifiable :-)