The place that documents all of the crazy ideas I have and all of the wacky projects that come from them.
I know you're probably like me and this thought hasn't even occurred to you, but I'm sure some of those projects are still in use at BYU and it's possible that some CS student could stumble upon your code and use it to cheat.I've never been a cheater and therefore don't think like one, but I did something similar while I was still in school a few years ago--I posted some of my code for some early CS classes I had taken. A faculty member somehow found it, and I was called in and accused of aiding cheaters. I had to swear innocence profusely and was warned that I could face disciplinary action by the Honor Code office. Luckily I came away without a record, seeing as they believed me when I said I didn't mean any harm.Anyways, just something to think about.
I hadn't really thought about that. I guess that I should take it down, but at least it gave me something to do for a little while because it is SO boring to stay home sick and just lay on the couch all day.
Of course the university can't do anything to you now that you aren't a student (I think), but I'm sure some faculty would not be pleased.It's interesting, I wonder if there is anything in _my_ old school code that is useful but not directly related to the assignment. It might be interesting to go back and look through it to see if there is any generic, reusable stuff that might be suitable for sharing. Maybe that will be my next sick day project :-).
So this is actually an interesting post about posting old code from classes on the net, and part of me now regrets taking down the code.
Post a Comment