Hey, remember that time when I said you shouldn’t set comestible rewards for coding failures? That was dumb. You should totally set comestible rewards for coding failures. And coding successes, for that matter. In fact, you should give yourself that kind of reward all the time! So let’s just pretend I never said that, k? K.
Alright, internet. We have a lot to catch up on. Last time I was here, I was about to start hacking into my Apache configuration files. I’ll get to that in a minute, but first, let’s zoom out to see what else has been going on over the past month. My last post was written and published from the back of a lecture hall during one of the most stultifying courses I have ever attended. Though the subject matter (C++) is interesting, the professor managed to render it into enthusiasm-draining drudgery, leaving my mollified brain with little desire to write code after hours. Moreover, I was just starting on a series of site designs with short, drop-dead-style timelines, a couple of which were in a new content management system. Though the sites look good now, and I have learned that I really like Expression Engine, free time was not in abundant supply. Mere excuses, I know, but there you have it.