Strict Standards: Redefining already defined constructor for class wpdb in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/wp-db.php on line 56

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/cache.php on line 36

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/cache.php on line 384

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el($output) in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el($output) in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/classes.php on line 541

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/classes.php on line 560

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl($output) in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl($output) in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el($output) in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el($output) in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/classes.php on line 659

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el($output) in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/classes.php on line 684

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/theme.php on line 540
Ongoing Process » 2007 » June

Archive for
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 26
June, 2007


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 26

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 26

A bike for me!


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 26
Sunday, June 17th, 2007

I love to go for bike rides, but I hardly ever do because standard bikes hurt me. The whole "hunched over" thing is hell on my back and wrists and bicycle seats seem to be specifically engineered to numb asses and crunch crotches. But I saw some guy in town yesterday on this amazing bike:

I’d never seen anything like it before. It took me a few hours of Googling to find it, but at last I managed to turn it up. It’s called a Dream and is made by a company called Day 6 (fauna, anyone?). It lets me sit straight up, provides back support, has a wide seat, and still uses mostly standard bike parts (so repairs won’t be a big deal). It’s hideously expensive, but I think it’s worth it if I can finally get out and ride. Especially on the incredible bike trails around Lake Champlain that I live right next to. I ordered it last night, and it’s shipping from Montana via FedEx (I presume ground). So hopefully I’ll have it early next week. I’ll let you know how it goes!


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 26

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 26

Battlestar Galactica is ending


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 12

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 21

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 23

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 25

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/10/d160031109/htdocs/ongoingprocess.net/wp-includes/functions.php on line 26
Saturday, June 2nd, 2007

So, the speculation is over and it is now official: Battlestar Galactica ends next season.

I am, of course, sad that it’s going and I’m sure as hell going to miss it when it’s gone. But I like that they’re ending it on their own terms. As they said in the announcement, “This show was always meant to have a beginning, a middle and, finally, an end.” I believe that’s the very best attitude to have. Every story ends, and the great ones end on purpose. We can look at The X-Files and Buffy to see what happens when a once great show doesn’t know when to wrap it up. I’m glad that won’t happen here.

Knowing that the end is nigh, I’m extra pumped to see next season. It’s not every day you get to watch the end of the greatest television show ever made.