A question was posed as to whether folks should fight for or flee from the Silicon Valley.
I answered that those who have bought homes here ought to fight for opportunities for the next group. The greater challenge is that a lot of folks who got theirs don’t want to make allowances for the next generations.
On the drive in this morning, I caught Forum’s program on the new dockless electric scooters that have been showing up in San Francisco. This service is a new take on dockless bike share. There is concern that users are riding on sidewalks, menacing pedestrians, and that despite state laws, they aren’t wearing helmets. Also, the scooters are often left blocking up the sidewalks.
The scooter proponent answered that since the scooters are a handy way to save car trips, San Francisco can continue its efforts to convert car lanes to bike lanes, where the scooters could safely scoot apart from pedestrians. That sounds great to me. The helmets, though … as I pulled up to the office, I emailed in a brief opinion. I then hung back from going into the office for a couple of minutes to catch the very end of the show. I’m glad I did. Michael Krazny closed with this:
We’ll leave it there! Well, except for one more comment about helmets that I want to read here, from Daniel, who says: “We should revisit the helmet requirement. Helmet use is a cultural convention. For example, they don’t wear helmets in Amsterdam or Copenhagen, which makes bicycling even easier in those places. It is safer to wear a helmet when riding in a car, yet we wouldn’t expect anyone to wear a helmet as a requirement to ride in a car.”
I think it would be nice to see these scooters in Peninsula suburbs, where we tend to lack good “last mile” transit options, and where there are fewer pedestrians to upset. Rental electric scooters sound like a better option than rental bikes in a lot of cases because they’re cheap to deploy, require less knowledge to ride, and require less storage space. And I suspect that the helmet requirement is probably unworkable.
I built a new system (from old parts) yesterday. It is a RAID10 with 4x 8TB disks. While the system is up and running, it takes forever for
mdadm to complete “building” the RAID. All the same, I got a little smile from this graph:
As the RAID assembles, the R/W operations take longer to complete.
The process should be about 20 hours total. As we get move through the job, the read-write operations take longer. Why? I have noticed this before. What happens here is that the disk rotates at a constant speed, but towards the rim you can fit a lot more data than towards the center. The speed with which you access data depends on whether you are talking to the core or to the rim of the magnetic platter.
What the computer does is it uses the fastest part of the disk first, and as the disk gets filled up, it uses the slower parts. With an operation like this that covers the entire disk, you start fast and get slower.
This is part of the reason that your hard drive slows down as it gets filled up: when your disk was new, the computer was using the fast-spinning outer rim. As that fills up, it has to read and write closer to the core. That takes longer. Another factor is that the data might be more segmented, packed into nooks and crannies where space is free, and your Operating System needs to seek those pieces out and assemble them. On a PC, the bigger culprit is probably that you have accumulated a bunch of extra running software that demands system resources.