Hah, I had a similar experience. Got kicked out of one class, changed to a keyboarding class because I could already type fast. Easy A, right? Well, the computers didn't work very well and I'd fix them, and leave a signature where I'd been. Teach was a little flabbergasted when I'd be sitting at a "broken" computer but no matter.
Don't tell, but I knew how to pop into windows and play games, and the machines were networked so I had everybody's classwork sitting right there. They can't catch you cheating when the assignment is to copy the same damned text. Teach lost me on day 1 when I did 65wpm on the 5wpm test, all like "no, you can't skip ahead, you've demonstrated can type at 5wpm, now you need to take the 10wpm test"
But then they taught us how to use macros in a word processor. I don't know how or why, but the computers had a shared namespace for these macros. We were only supposed to use them, but I figured out how to make and edit them. Told a friend about it. The friend promptly changed the macro the class was meant to use. With recursion. And that was Trouble. Who gets the blame? Kid with their name on all the autoexec.bat files, that's who.
Shortly after I got back from suspension, I talked to the IT guy, and became his unofficial TA, and fixed computers during that class period.
> I don't know how or why, but the computers had a shared namespace for these macros.
They were saved in the "normal" document template, probably, I guess shared to the network drive. My first tech job was interning with an insurance company which had some important VBA script saved in the template. I want to be charitable, but it was almost certainly out of cluelessness... the macro even included a check to only do anything when run from a specific document, so it's not like it was meant to run from every document.
Of course I didn't realize this and it bit me when I dutifully made a copy of the document before editing the macro... only to break something in "production" (or what passed for it...) and get yelled at for it.
Tangentially, not too long thereafter I replaced most of my job (and that of half my six-person team) with a short M4 macro (secretly, of course). Freed up many hours during the workday to work on my Perl chops and figure out how to get one of those sweet "GMail" invitations.
Don't tell, but I knew how to pop into windows and play games, and the machines were networked so I had everybody's classwork sitting right there. They can't catch you cheating when the assignment is to copy the same damned text. Teach lost me on day 1 when I did 65wpm on the 5wpm test, all like "no, you can't skip ahead, you've demonstrated can type at 5wpm, now you need to take the 10wpm test"
But then they taught us how to use macros in a word processor. I don't know how or why, but the computers had a shared namespace for these macros. We were only supposed to use them, but I figured out how to make and edit them. Told a friend about it. The friend promptly changed the macro the class was meant to use. With recursion. And that was Trouble. Who gets the blame? Kid with their name on all the autoexec.bat files, that's who.
Shortly after I got back from suspension, I talked to the IT guy, and became his unofficial TA, and fixed computers during that class period.