In 1996, I left teaching and pursued a degree in computer science. I spent the next five years sitting at a desk talking only to a computer in a language called āC++.ā
Programming was the opposite of teaching. I liked the fact that the computers, though often disobedient, never talked back.
Programming was the opposite of teaching. I liked the fact that the computers, though often disobedient, never talked back. If a computer became impossible to work with, I wouldnāt think twice about doing the equivalent of a One Flew Over The Cuckooās Nest frontal lobotomy by wiping clean the contents of the hard drive. The best part about being a computer programmer was that, unlike being a teacher, I didnāt have to take anything home with meānot papers, not emotions.
As a beginning computer programmer, I started with one of the most tedious and uncreative assignments. I was a level one debugger for a desktop publishing program. Commercial software, I learned, is generally released with thousands of errors or ābugs.ā Though a team of testers tries to find them before the software is shipped, many bugs still slip by. Home users, who pay $500 for the privilege of using the crash-prone programs, locate the remaining bugs and call the company to complain.
When enough calls are logged about the same problem, a debugger is notified. Back then, Iād read the heading of the ābug reportāāsomething like, āProgram crashes when you push enter, backspace, and shift at the same time while saving a file.ā It was not my place to ask why anyone would ever find themselves doing that, let alone take time to report the bug, but dozens did. The first step in fixing a bug was to make sure it wasnāt a false alarm. Iād push this ridiculous combination of keys in an attempt to crash the program. I always feared that one day Iād see a bug report reading, āProgram abruptly closes when user sticks the mouse up his nose.ā
If I could successfully crash the program by following the steps, Iād have to comb through a million lines of computer code to fix it. Otherwise, Iād close out the bug with the three-word explanation, āUnable to reproduce.ā Ironically, this was also an accurate description of my social life at the time.
When I was a teacher, I was always looking at my watch and thinking, āHow did this period go by so quickly?ā As a programmer, I would do the opposite.
Not like teaching at all. When I was a teacher, I was always looking at my watch and thinking, āHow did this period go by so quickly?ā As a programmer, I would do the opposite. Ten times a day, Iād estimate the time and then compare it to the actual time. If the real time was significantly later than the time I thought it was, Iād get a little thrill.
Another way Iād make the time go by more quickly was with something I could never do as a teacherāuse the bathroom. At the slightest hint of discomfort, Iād be off to the bathroom for a ten-minute break. On the way back, Iād stop by the cooler and refill my water bottle, in anticipation of my next bathroom break.
Still, I never completely separated myself from teaching. At night, I taught computer programming at a college. Over the summers, I continued volunteering at teacher training programs, presenting the ideas from this book. I was a teacher in a computer programmerās unstylish clothing.
The main result of my five agonizing years as a debugger was that I became much more marketable. Even though I hated being a computer programmer, I thought that if I could land a job in the financial district of Manhattan, I could at least make a lot of money while hating it.