Come exam time, we were allowed to use our calculators. I asked if I should clear mine out given I had a program which could "cheat" (I was a teachers pet). He said something to me (privately) along the lines of, "don't worry about it. the way I see it, you've already proven to me you know the content." Ironically, today I could probably piece together a TI83 assembly program from memory, but I couldn't even tell you what Newton's Method does, let alone how to do it. Not sure what lesson to glean from that.
I remember eating lunch one day, maybe a year or so later, in his classroom with some friends, and he was browsing around the internet trying to find a job I'd like in math. Looking back, I find it funny that he was landing on things like "actuarial science" and "accounting" instead of the obvious. I think that was his way of trying to make up for the piss-poor guidance counseling in my school of 80 people in the middle of nowhere. I ended up wasting a semester in Computer Engineering doing CAD and coding MatLab before a professor took me aside and basically said "you're finishing these matlab assignments faster than my grad students would. Are you sure you don't actually want to do Computer Science?"
It sucks to see this. The accessibility of coding today has never been better, so I'm not going to pretend like this is a doomsday thing for helping kids get into the field, but it did have power in its ubiquity. Teaching computer science in high schools isn't a tenth as effective as students coding up a program to make their math classes easier, or modding CounterStrike after hours, or "hacking" the school computer labs to play Halo with their friends. Technology, and the ability to shape it to help us, should be ubiquitous. It shouldn't be thrown out the window just so one teacher can more easily proctor a hundred tests instead of twenty.