hahaha, ok, so for some reason the premier of Saul of the Molemen on
Adult Swim cracks me up. I ran home from the lab last night so I could catch it. A little shorter than I anticipated but I think it might be a funny but short series.
Last night was the due date for the first project for the professor whom I work for at Tech. I missed a block of office hours last week so I felt compelled to compensate but holding hours the night of the due date. I figured, everyone should be done, few questions here and there, great time to finish some homework. Boy I was wrong. I think about a 1/3 of the class showed up! So as I was running around the lab answering
Web-Cat questions. Suffice to say I'll be doing my homework tonight.
But on another note, I couldn't help but think back to when I took the class 4 years ago. I recall having a difficult time as well because
JUnit testing just seemed dumb to me then. Having to test every aspect of your code is a great idea, don't get me wrong, but it slows down development. Especially if you have to write 10 times more code than necessary to test it. Ontop of that Web-Cat was new and no one knew how to debug its cryptic messages that would make you search for bugs in random places of your code. Even last night, I was confused with half of what it was spewing out. The only good thing I recognize is the unlimited submissions. But as of last night, seeing some of the reactions and the tempers of some of the students I couldn't help but think to myself "I've been there". I took Data Structures in the summer which about killed me physically due to lack of sleep and extremely poor diet. I even recall having to chug soda for OS, junior year, when I sprinted across campus to catch my professor's office hours because I stayed up all night and couldn't figure out my process scheduler at first.
So I decided to list a few things that I feel were essential
1) ssh + Vi
I couldn't stand GUIs, too distracting for me.
most people who know me would agree.
2) cout, echo, System.out.print
statements that helped me avoid messy debuggers
3) reading the project spec 3 times before I touch the keyboard.
I had a bad habit of jumping in and coding before I knew all the details
bad idea. I like the quote: "If you don't understand it, you can't program it"
4) Not skipping class
my professors always gave hints in lecture, rewarding those who were learning
and not programming atm I guess.