Life is almost always a whirlwind of madness

January 29, 2007

Well, I got my Beanpot tickets, but not much else seems to be in order, these days. It’s probably some of my unhappiness that causes me to procrastinate even more than usual, but sometimes it seems like there’s nothing I can do about either. I’m kind of happy to have this blog as a way to just get my feelings into words, even if my only consistent reader seems to be my mom. But hey, that’s how Aaron Gleeman started also, right?

I’m a bit worried about the Terriers without John Curry in net. Gillespie did a fine job against UMass after Curry was pulled, but that’s UMass, not a team like UVM or UNH. I know Curry is still the starter, but I have to wonder if he’s hurt or just worn down from playing a lot of games.

The Perl tutorial I went to on Friday might’ve been the most boring thing ever. I know it was an introductory tutorial, but they need to decide whether they want it to be for people with programming experience or not. The first hour was basic programming language type stuff, but the instructor made comparisons to C, in which case, if people should know C for the tutorial, then why are we spending an hour on maybe 15 minutes of material? Oh well, the regular expressions thing was interesting, at least. Hopefully tomorrow’s CSS tutorial is much better.

One last note: It prides me to see Philip Hughes show up strong in this study of types of minor league pitchers. I am excited for his major league debut, when it happens. I think the kid will easily make everyone stop talking about Roger Clemens.

Advertisements

Coding 101, by John Keklak

October 6, 2006

After my CS411 class this week, I am completely inspired to post what must be made clear as a message to the world courtesy of the teachings of one John Keklak. And that is coding standards. So here we go:

  1. Indentation with discipline. Not only must you indent every time you start a new line, but you want to make sure your code makes the person who reads it feel like they’re being punished by reading the code. After all, we don’t just write code. We go through a process. For example:
  2. int getNumTasks(table){
    int a = numRows(table);
    return a;
    }

    Now this, who can read this? I mean it’s a bunch of gibberish and really, what do I get out of it? But take this example:

    int getNumYOUREANIDIOT(GO TO THE CORNER OF THE ROOM){

    int YOURENOTALLOWEDTOWATCHTVTONIGHT = YOURE PATHETIC!;

    return YOUREGOINGTOBESERVEDTOTHESHARKS;

    }

    Not only is that readable, but it tells you a message. And it disciplines the reader. I can’t tell you how much that makes coding in real projects go much quicker. Pink slips have disappeared thanks to this method. Read the rest of this entry »