Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
Warning: mktime() [function.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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 378
Warning: strftime() [function.strftime]: 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 'UTC' for 'UTC/0.0/no DST' instead in /usr/local/www/grapefish.org/blog/files/rapidBlogHelpers.php on line 365
steps to a better world, part III
2009/06/09 17:36
| blogs
Give Fair Warning
This one is pretty simple - give a heads up when something kooky is on the way. You'll know when, and when you know, warn the people it'll affect.
One of the ways in which the world could so easily be made a better place is to have people use their fucking turn indicator while driving a car. Every time.
This one is pretty simple - give a heads up when something kooky is on the way. You'll know when, and when you know, warn the people it'll affect.
One of the ways in which the world could so easily be made a better place is to have people use their fucking turn indicator while driving a car. Every time.
comments
last day dream
2009/05/21 11:19
| blogs
A brilliant short film from Chris Milk.
"Last Day Dream" a man watches his life pass before him
From Daring Fireball.
leaving out the winner
2009/05/17 23:20
| blogs
Here's what the top 10 places on this chart would have looked like had they included Nintendo in their rankings.
Google clocked in at a little over $200,000 in profit per employee, but Nintendo made a staggering $1.6M per employee in the same year.
From Daring Fireball.
Google clocked in at a little over $200,000 in profit per employee, but Nintendo made a staggering $1.6M per employee in the same year.
From Daring Fireball.
steps to a better world, part II
2009/05/15 08:40
| blogs
Do no harm.
I used to call this one "leave things as you found them", but have since modified it slightly to emphasize the idea that, at the very least, you should endeavor to leave things in no worse condition than you found them.
There are plenty of everyday examples, not the least of which is making some small effort to avoid darkening anyone's day by their having had the fortune of encountering you. The next step, actually trying to improve the condition of the spaces through which you move, is the logical one to take.
I used to call this one "leave things as you found them", but have since modified it slightly to emphasize the idea that, at the very least, you should endeavor to leave things in no worse condition than you found them.
There are plenty of everyday examples, not the least of which is making some small effort to avoid darkening anyone's day by their having had the fortune of encountering you. The next step, actually trying to improve the condition of the spaces through which you move, is the logical one to take.
logic and emotion
2009/05/10 09:41
| blogs
A good article on engineering and design, with Google as the example, from Lukas Mathis at ignore the code.
steps to a better world, part I
2009/05/06 19:45
| blogs
Mind your business.
At least a little explanation is in order here. I don't say "mind your own business", because sometimes, minding business that is not your own is what you should be doing. The important part is that your affairs are minded - taken care of. That you should keep your nose out of others' issues is unimportant.
Take care of what's on your plate, and let the others take care of theirs.
At least a little explanation is in order here. I don't say "mind your own business", because sometimes, minding business that is not your own is what you should be doing. The important part is that your affairs are minded - taken care of. That you should keep your nose out of others' issues is unimportant.
Take care of what's on your plate, and let the others take care of theirs.
why some old habits die hard
2009/04/27 18:08
| blogs
I ask myself sometimes why I continue to read slashdot, and then I come across a comment like this that explains it to me:
See, this is exactly why I adore /. Name one other popular site where you'd get ten bites on a troll that 99% of the population doesn't even understand.And from later in the same conversation:
Right down to the Where is the "Ignorant" mod tag? signature. 10/10 for you, sir.
I read slashdot because after all these years, it still makes me laugh.Monster cables, dude, Monster cables...
>Nah, I tested some ethernet cables I made with 4 pairs of wire coathangers and they performed just as well as the Monster Cable ethernet cord!
rest assured
2009/04/07 12:18
| blogs
Every living creature over the approximate level of a jellyfish has an agenda.
site relaunch
2009/03/25 20:55
| blogs
New logos, a partial redesign, and perhaps more frequent posts are all in the offering. Stay tuned, and do let me know what you think.
The logo is already updated for much of the site, and it sure is easier to render in greyscale, but it's a bit more complicated to use on varying site backgrounds, because I went and used the Alpha channel. That'll teach me.
The logo is already updated for much of the site, and it sure is easier to render in greyscale, but it's a bit more complicated to use on varying site backgrounds, because I went and used the Alpha channel. That'll teach me.
burning earth's blackened past
2008/09/22 01:11
| blogs
Tim Bray on Driving:
Like most people on the left half of the New World, driving has informed and constrained and enriched my adult life. I’ve enjoyed it. Indications are that mine will be one of the last drive-everywhere generations. The shape the tribe settles into may be more pleasing, and strengthening local culture is a fine thing, but the loss of the time-behind-the-wheel, with the music playing, going places, well, it’s sad.Tim goes on to describe ups and downs of daily driving, but the above stands well on its own.One time years ago I even wrote a terribly long (pages and pages) poem about driving; here’s the beginning:
To walk is best of course. And I
would rather drive than fly. Would turn
Earth's curve beneath my tires. Would burn
Earth's blackened past in engine fires;
burn time that space is measured by
from edge of map to edge of sky.
From ongoing.
the darnedest things
2008/08/05 21:19
| blogs
Like Iron Chef before it, a lot of the charm of the Japanese game show Sasuke (Ninja Warrior) comes from the commentators. It is, at times, likely a function of translation, but the end result is the same. You don't hear stuff like this on American television:
"I wonder if Bruce Lee would wear such tight orange shorts."
You can catch Sasuke on the G4 network.
"I wonder if Bruce Lee would wear such tight orange shorts."
You can catch Sasuke on the G4 network.
2008 box office chart
2008/08/03 13:11
| blogs
This intriguing bit of data visualization from Zach Beane illustrates the box office revenue from major movies released in 2008.
There are more charts available back to 2005, and some top ten's from 1998 and 1988.
From Kottke.
There are more charts available back to 2005, and some top ten's from 1998 and 1988.
From Kottke.
iphone 3g
2008/07/29 09:03
| blogs
I may have more to say on the 3G later on, but for now Jesper has it covered with this bit of humor.
juxtaposition
2008/07/29 07:29
| blogs
Diana Kimball goes on an eloquence jag in explaining what she's learned so far about being an internet geek.
Deeply insightful, delightful writing; I don't remember being so captivated by prose since I read Mark Helprin's Winter's Tale, which has little (if anything) to do with the internet or nerdishness. I encourage you to enjoy both.
For Kimball's piece, you'll need about 10 minutes. For Helprin's novel, perhaps 10 days. Both, though, should last far longer after you've read them.
Kimball's blog is from Big Contrarian.
Deeply insightful, delightful writing; I don't remember being so captivated by prose since I read Mark Helprin's Winter's Tale, which has little (if anything) to do with the internet or nerdishness. I encourage you to enjoy both.
For Kimball's piece, you'll need about 10 minutes. For Helprin's novel, perhaps 10 days. Both, though, should last far longer after you've read them.
Kimball's blog is from Big Contrarian.
riffing with numbers
2008/07/18 06:43
| blogs
Jacob Seidelin took up Radiohead's House of Cards data-fed video and reinterpreted it with JavaScript and Canvas. He had to cut down the data size quite a bit, and some browsers still have a hard time rendering it fast enough, but it's a nifty bit of web coding.
Jacob's blog is Nihilogic.
Jacob's blog is Nihilogic.
flip video camera
2008/07/15 10:12
| blogs
Merlin Mann's recent post Ellie in the Park puts into perspective why I want one of these silly little Flip camcorders.
I'm not usually one to take or even look at snapshots or video, but I've been doing a bit of it at the track when I think of it, and looking back on them as I sometimes do makes me realize I've given photography of both sorts less attention than I perhaps should have.
A cheap, pocketable camcorder seems to fit the bill in more ways than one. Like Merlin points out, you're far more likely to have it with you when "nothing" is happening, and you may just shoot that nothing, and have it end up being important to you later in life. It's about capturing the in between moments, the everyday, the common.
Since I don't put much in to my photography efforts, I don't compose the snapshots from the track in any real sense of the word. Some of them turn out OK, though, at least to me. Maybe I can form some sort of noticeable style based wholly in ambivalence. That, or I could possibly become the first director to shoot a full-length motion picture on $129 video cameras, and probably $500 worth of AA batteries.
From Kung Fu Grippe.
I'm not usually one to take or even look at snapshots or video, but I've been doing a bit of it at the track when I think of it, and looking back on them as I sometimes do makes me realize I've given photography of both sorts less attention than I perhaps should have.
A cheap, pocketable camcorder seems to fit the bill in more ways than one. Like Merlin points out, you're far more likely to have it with you when "nothing" is happening, and you may just shoot that nothing, and have it end up being important to you later in life. It's about capturing the in between moments, the everyday, the common.
Since I don't put much in to my photography efforts, I don't compose the snapshots from the track in any real sense of the word. Some of them turn out OK, though, at least to me. Maybe I can form some sort of noticeable style based wholly in ambivalence. That, or I could possibly become the first director to shoot a full-length motion picture on $129 video cameras, and probably $500 worth of AA batteries.
From Kung Fu Grippe.
rockin' with the lab gear
2008/07/09 17:08
| blogs
A curiously engaging music video for a piece of lab equipment, apparently something of a trend among manufacturers of such apparatus.
Gotta get people excited about buying automated pipette machines somehow, I suppose.
Again, from Big Contrarian.
Gotta get people excited about buying automated pipette machines somehow, I suppose.
Again, from Big Contrarian.
glückliches herrentag!
2008/06/12 13:19
| blogs
In Germany, there is no Father's Day, as such. Celebrated instead each Ascension Day is Männertag, or Herrentag, a day on which men haul Bollerwagen (small carts) full of beer, wine, sausages, cheese and so forth on a hike and then consume the contents.
Isn't that a lot like every day in Germany? At least in my imagination, it is, and if I lived there, I would endeavor to make it so.
Lift a liter this weekend to celebrate, and happy father's day to those of you who are.
Isn't that a lot like every day in Germany? At least in my imagination, it is, and if I lived there, I would endeavor to make it so.
Lift a liter this weekend to celebrate, and happy father's day to those of you who are.
comments system
2008/06/08 08:44
| blogs
Blogger now provides a comment service for grapefish.org's blog. Let me know what you think of it!
no flash on the iphone
2008/02/13 04:22
| blogs
John Gruber at Daring Fireball, on why he believes there will be no Flash support on the iPhone.
His reasons are convincing, and I agree with them. In particular:
His reasons are convincing, and I agree with them. In particular:
The mobile market is wide open in ways that the desktop market is not. E.g., in the mobile OS market, Microsoft isn’t even in first place, let alone a monopoly. And, in the mobile world, Flash is rare, not ubiquitous. Why would Apple help Adobe establish Flash as a de facto standard for the mobile web, too?
remember that time...
2008/02/13 04:05
| blogs
positive outlook
2008/01/03 18:36
| blogs
John Gruber at Daring Fireball has a better outlook on the turning of the year than I did, evidently.
rss link changed
2007/11/28 08:34
| blogs
If you subscribe to the
, you'll need to re-subscribe as the link has changed (this was done for compatibility with certain browsers). Thanks!
roundcube beta
2007/11/27 11:30
| blogs
RoundCube Webmail is in beta here at grapefish. If you have a mail account, simply log in as normal and give it a try. Be sure to let me know what you think.
open webmail
2007/11/25 13:40
| blogs
I got the last of the changes to the OWM access links straightened out this morning, so everything should be working the way you'd expect. Sorry about the disruption.
site redesign
2007/11/24 01:16
| blogs
So I finally got serious about redesigning the site. I do hope it looks a little better than before, even if it fails to evoke the grape-ness that is the core of the fish. Or something like that. Maybe I just don't like purple.
In any event, do enjoy your brief time here on the home page.
In any event, do enjoy your brief time here on the home page.
ical data now available
2007/11/23 23:35
| blogs
I have published iCal format calendars for Eden and myself; if you're interested in keeping tabs on when we're busy and when we're not (so you can invite us to fabulous events etc.) you can subscribe to them with Google Calendar, iCal in MacOS, or any other calendaring app that understands the iCal format.
Here are the URIs:
http://webdav.grapefish.org/Patrick.ics
http://webdav.grapefish.org/Eden.ics
Here are the URIs:
http://webdav.grapefish.org/Patrick.ics
http://webdav.grapefish.org/Eden.ics
