[RAndoMness]=> 28Sep09
 [JPsDocs] => 22Feb09
 [JPics] => 10Dec11

February 2020
sun mon tue wed thu fri sat
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
recent music
Boycott SONY



    print_r($meaninglessGibberish);//...  echo $newRAM;
    added Fri April 15 2005 at 11:44 AM
    Today's entry on Michael Kaplan's blog (I read Microsoft programmers' blogs at work, because that almost feels productive when I feel like being unproductive) somehow reminds me of my own development. Of course, I'm no OS programmer, and I've yet to even *cause* a blue screen of death (albeit I've had my fair share of run-time errors). In fact, I'm not sure why his entry reminded me of making my website, which is why I'm posting it here and leaving a link there instead of just leaving a comment on his site.

    Because, well, as I'll say a few more times in this entry, it's my site so I can do whatever I want.

    Everybody's first reaction to seeing my site is that with all that technical gobbledy-gook (real technical word), it looks like there was some kind of mistake in loading the page. My brother took one look at it and recognized the theme as PHP debugging, and asked what the problem was. For PHP programmers (if anybody even classifies themselves as a "PHP programmer"), my page is equivalent to a mix of the blue screen of death and lazy, live debugging.

    I'll tell you what, though, I worked at making it look that way. Like it or leave it, I do believe that I did succeed at making a unified theme for my site. Of course, it is long overdue for a major overhaul. Having the same design for 15 months is remarkably long, especially since I've been learning so many cool JavaScript and CSS tricks that I could play with. And I need to get an RSS feed constructed. The first thing to get axed revamped will almost certainly be JPics and the daily background. I started an iteration of this a couple weeks ago, but I find myself getting horribly off topic.

    As some of you may have noticed before, when I do make changes, I work on the live server. I don't have a demo server to work on, and I don't get enough traffic to make it worth doubling everything just for development purposes. Of course, this potentially results in the end user (that's you) seeing messages like "Error parsing line 206: unknown error parsing index.php" or whatever the current PHP error message is. At least I haven't started putting my contact information on error pages yet, so that slows down the calls for help.