What’s been going on with my bus?

I think I finally figured out what’s been going on with Metro’s route 372 (Woodinville P&R to University of Washington) in the mornings. Before today, I always made it out to the stop by about 8:25AM or so and managed to catch the bus about 8:30AM, which got me on campus on time for work at 9. However, yesterday, I got stuck waiting until 8:40, which made me ten minutes late for work.

Of course, this prompted a check of the time schedules Metro posts for that route – there are two arrivals: one at 8:15AM and one at 8:40AM (the 8:15 is the one I took in this morning, which was on time). So why was it that standing there at 8:25 let me catch the 372 at 8:30? Either the 8:15 ran 15 minutes late for over a month (I started riding in July, and yesterday was the first time I got stung), or the 8:40 was/is chronically 10 minutes early. Either way, this is completely against their time schedules and led me to think that it was actually an 8:30 bus.

Good going, Metro.

File Servers: Dead? Not Really.

Joel Oleson (a member of the MS SharePoint Products and Technologies Team) wrote earlier this year on whether the file server is dead or not. A lot of the points he makes about what should and shouldn’t be stored on SharePoint servers are fairly obvious – don’t do application or hotfix rollouts using SharePoint, for example – but some of them were a bit surprising or at least worth mentioning.

  • Storing SQL databases as a SharePoint object doesn’t really make sense; linking these in via the Business Data Catalog functionality does.
  • Just because Access 2007 files can be stored in SharePoint doesn’t mean they should be stored in SharePoint. This depends largely on the complexity of the database and how it’s used.
  • Direct quote: “Access 2003 databases should not be stored in SharePoint document libraries where multiple users need to edit the access database simultaneously.”
  • SharePoint is not developer source control, though the terminology and functionality is roughly the same.
  • If Excel spreadsheets have data that cross different spreadsheets, this may cause issues due to how file paths are encoded when those dependencies are created.
  • File storage: cheap. SharePoint storage: expensive relative to the cost of file storage (since almost everything’s stored in a database).
  • Basically, if it’s a collaborative file share, SharePoint can replace it. However, if it’s simply file storage, this may not be cost-effective.

Joel has a follow-up post here – some further bullets:

  • Having users completely copy over all their private documents into My Sites or Team Sites isn’t what you want to have happen.

There are plenty of others talking about the same subject (see the links Joel provides). This additional commentary isn’t bad.

Subsite Searches in SharePoint Not Working

We’ve been having a search configuration problem within SharePoint 2007 at work in which the “This Site” and “This List” search scopes available within any site haven’t been returning results, despite the fact that the global site search will very clearly return results with the exact same query. This seems to be an issue that several people have on TechNet’s Sharepoint – Search forums. A bit of digging discovers a recent post by Robin Meuré, which suggests that using https:// (SSL) might be the issue. I’m a bit dubious, but I’m running it by our system administrator to see if it even makes any sense.

Nice Seattle Neighborhoods

I typically ride Metro’s route 65 along 35th Avenue Northeast through both Wedgwood and a very small part of the View Ridge neighborhoods on my way home after work.  I’ve decided that between Northeast 45th (which runs past the University of Washington) and Northeast 110th is a very nice area with fairly nice houses (chances that any of those are rentals seems rather low).  Smaller houses, but that’s typical for Seattle.  The drawback being that that corridor is only served by routes 64 and 65, though some cross streets are served by other routes (not many of them, from what I can tell).

Seattle: Transit Woes with Intellectual Energy Wasted

Living in Seattle at the moment is both weird and a bit scary. Scary because the Washington State Department of Transportation is currently ramping up to a major shutdown of a portion of Interstate 5 just south of downtown Seattle for major repair work between the 10th and 29th of this month. This is being billed as one of their biggest projects ever. Weird because, the way I look at it, it’s sort of a traffic armageddon, but it’s also a major opportunity for the City of Seattle that’s being grossly neglected.

Businesses are responding by trying to make it far easier for employees to get to work by offering telecommute or shared commute options, even promoting use of transit via our local transit agencies (Metro, Sound, and Pierce Transit, specifically). Metro, rather glaringly, doesn’t have any extra capacity to add in case it gets slammed, while other agencies seem to have some surplus. But this is truly strange in that, despite exhortations from the Department of Transportation to avoid commuting through that particular stretch of I-5, nobody seems to see this as a prime opportunity to rethink the way that Seattle itself is organized.

We have a number of major traffic arterials that are slowly aging and will be in desperate need of replacement within the next 20 years. One of the biggest is the Alaskan Way Viaduct, which is way over capacity; another is the Highway 520 floating bridge, and Interstate 5 ranks high in that list. Political fisticuffs have been flying around the subject of replacing both the Viaduct and the floating bridge, with people arguing quite vocally about construction methods and timeline. These are vital infrastructure – or so we think. I can’t argue that the floating bridge doesn’t provide a major west/east corridor – of course it does. But what if we sat down and re-visioned the idea of Seattle and the communities surrounding it? What if we decided that, instead of expending our mental energy and our physical resources on reconstructing these resources, we increase population density in Seattle’s downtown core, massively improve transit presence throughout Seattle, and offer disincentives to drive downtown (imitating London and cities in Germany)?

The problem is, we sit around debating. Some of the most drastic rethinking of what it means to be in a city comes from politicians that take immediate action without allowing time for debate. Yes, Interstate 5 is being repaired, and it will undoubtedly be a mess. So why are we ignoring the chance to rethink what it means to live here rather than simply saying “things will get worse, deal with it”? Why do we push this off until the Viaduct closes and we are faced with much the same problem?

QuickPlanner

After a couple hours of tweaking, I give you my somewhat elegant hacking of the Trip Planner application, produced here in PHP. Not the prettiest code, and I’m sure there’s several security holes, but it works. I’m going to try it out on my Blackberry when I get the chance.

Update: <bait> I’m now wondering what Sean would say. </bait>

Planning Bus Trips Just Takes Too Long (on my ‘berry)

As much as I love King County Metro’s Trip Planner utility for figuring out what bus routes I need to take to get to a particular place, loading this site on my Blackberry and entering information is more than a little time-consuming (and I’m often doing it right before leaving for a particular destination). Thus, I’m going to create a slight hack by using my own PHP script to post parameters into the Trip Planner.

Devious? Perhaps…

The Source of Bottled Water: That’s Not The Problem, Really

It seems like people miss the point entirely when they worry that companies selling bottled water don’t make it clear where that water comes from. The problem isn’t really the source – the problem is that they’re selling bottled water in the first place. There’s a huge difference between water bottles that are typically bought and used once and, say, my trusty Nalgene bottle that follows me all over the place and always has fresh water in it.

Not that I’m not guilty of buying bottled items – I do occasionally indulge in a Nantucket Nectar or two, which are sold in glass, not plastic, bottles. I’ve also been known to make a hapless coffee cup go on a nice, long journey to the landfill. But there’s something about bottled water that just seems somewhat redundant. The fact that it puts tons of plastic into the waste stream is a very large drawback, but the fact that major brands may simply be purifying municipal water sources and shipping it elsewhere has its own set of problems – the energy used in bottling and transportation alone greatly outweigh just drinking from the tap in the first place. You can always get a water purification system, though these systems are problems in and of themselves.

Update (August 1, 2007): The New York Times makes a slightly stronger case on this issue than I do.