Progression

We had the hole in the driveway fixed…

fixing the driveway hole

Then we built sukkot and handled other chores…

tools in bucket

…and the peasants rejoiced (possibly with a bit too much raspberry tort.)

rasberry tort

Some art was framed and hung…

IMG_0153.jpg

And some things were noted for later…

bulletin board

Some of the yard was left to overgrow…

overgrown yard with bamboo

Then there was more cooking, and as always…

cooking

There was more work to do…

IMG_0191.jpg

And so the month has gone. Looking forward to October… now just around the corner.

★ Then Welcome to Android

★ Then Welcome to Android:

Google vice-president for engineering Vic Gundotra, on-stage at the I/O developer conference in May, regarding why Google created Android:

If Google didn’t act, it faced a draconian future where one
man, one phone, one carrier were our choice. That’s a future we
don’t want.

Skyhook Wireless, in their “complaint and jury demand” filed against Google yesterday (I’m hosting a copy of their entire filing (PDF), and I highly recommend you read it — it’s not long, and is written in pretty straightforward plain language), regarding Google’s control over which devices have access to the Android Market:

22. Google’s established practice in determining Android
compliance consists of two steps. The first step requires each
Android-enabled device, and its embedded software, to be run
against the Compatibility Test Suite (CTS), a software-based
test platform that objectively evaluates whether the device
and software are compatible with the published Android
specifications. The second step involves a review of the
device and software based on an amorphous outline of
additional, non-standardized requirements known as the
Compliance Definition Document (CDD). This entirely subjective
review, conducted solely by Google employees with ultimate
authority to interpret the scope and meaning of the CDD as
they see fit, effectively gives Google the ability to
arbitrarily deem any software, feature or function
“non-compatible” with the CDD.

23. On information and belief, Google has notified OEMs that they
will need to use Google Location Service, either as a condition
of the Android OS-OEM contract or as a condition of the Google
Apps contract between Google and each OEM. Though Google
claims the Android OS is open source, by requiring OEMs to use
Google Location Service, an application that is inextricably
bundled with the OS level framework, Google is effectively
creating a closed system with respect to location positioning.
Google’s manipulation suggests that the true purpose of
Android is, or has become, to ensure that “no industry player
can restrict or control the innovations of any other”, unless
it is Google.

Vic Gundotra, at I/O:

If you believe in openness, if you believe in choice, if you
believe in innovation from everyone, then welcome to Android.

[I’ve really got nothing to add. It should be no surprise that Google the enterprise acts like an enterprise. Just keep it mind when you use their “free” services. If a service is free, then you are the product. And this applies to all companies. Caveat emptor was never so applicable.]
Source: Daring Fireball

The week in links (09/20)

Gravel road riding tips from Ira Ryan

Lifted in its entirety from OregonLive.com… scroll to the bottom. Below, the photo is by Robert Crum (http://flic.kr/p/5GtV7m)

Gravel road through autumn woods.jpg

[BTW, while the long epic gravel grinds are amazing rides, doing shorter, supported gravel road rides are incredibly awesome too. Don’t miss out just because there isn’t en “epic” ride near you. Find some gravel and go!]

Ira Ryan, two-time winner of the 300-mile Trans-Iowa gravel road race and Portland bike builder (iraryancycles.com) has some gravel survival advice for you.

  1. Bring extra tubes, patch kits and a dependable frame pump that inflates up to 100 psi.
  2. Have good gravel tires (hybrids between road racing and touring tires) that are wider and with a Kevlar puncture strip in the tire casing. They should roll fast with a minimal tread pattern for the smoother sections of road. Maintain near-maximum tire pressure to resist pinch flats.
  3. Have a comfortable bike. A good gravel bike fits like a comfy road bike but with more clearance for wider tires and a little mud. Cyclocross bikes are a good start. 29ers and other mountain bikes are often overkill unless the gravel turns into single track or gets very rutted.
  4. Be loose on the bike. Gripping the bars and trying to fight the gravel will only result in a crash or sore muscles. If you move your weight back on the saddle, the front wheel will glide over a loose section.
  5. Keep your overall weight down by carrying less and thus decreasing fatigue during a long gravel event. My good friend G. Pickle, who raced in the first Trans-Iowa race, told me to “travel light and freeze at night.”
  6. Music can be helpful. It has saved me at 3 a.m. when all I wanted to do was sleep in a ditch. Justin Timberlake and Deelite got me through the third Trans-Iowa. Be sure you can hear traffic.
  7. Stay fueled and hydrated. Dusty gravel makes water that much more important. Don’t be afraid to eat a burger for long-burning fuel.
  8. Stay flexible. Yoga and stretching during and after your ride help a lot by keeping your body from locking up.
  9. Make good lines and use extra power to get through loose gravel. If you steer with your hips, push hard on the pedals from the back of the saddle and use the front wheel as a sort of rudder; you can clean most deep, loose gravel.
  10. Train and refine your mental stamina for really long gravel races. If you get overwhelmed by the distance of an event, just focus on the here and now of the road. Ride at your own pace, take your time, and keep pedaling.