Flickr vs Instagram vs Wordpress.

Flickr’s galleries have long been one of the tools available to our community for visual storytelling, though they have gotten dusty over time as the rest of the site progresses. So today, we’re happy to announce that we’ve begun to roll out a fresh Flickr galleries experience, where we help you tell your visual stories…

via All new Flickr galleries — Flickr Blog

Flickr just announced some long overdue updates to their Galleries page. It’s good to see continued investment in the Flickr platform. It also comes at a time when I am working to reduce the number of creative sharing platforms I use, so it’s useful to consider whether Flickr will continue to fill a space for me.

I still find Flickr my place to share the intentional photos, the “work”, that I want to create. It’s not perfect. The 1300 photos in my Flickr stream need to be curated into a more consistent body of work that’s more tightly focused on the subjects I find most interesting. Its likely there is less than 1/3 worth keeping. but that’s a rainy weekend project for the future.

I use Instagram too. There you’ll find snapshots of pets, concerts and friends cropped to 1×1 and filtered just so. I know many photographers have found a home there but something about the smaller, mobile experience doesn’t feel right to me. I’m not sure I could present a work or a cohesive collection there. My Instagram also needs the cobwebs of bad photos deleted away, a task that IG’s tools make difficult.

Ideally I’m going to create a new portfolio site here on WordPress to be my “best of” portfolio site. Pushing myself to edit from 100 shots to 10 good photos and then down to 1 great (to me) photo won’t be easy. Still it is where I need to go to become a better photographer.

Instagram would be for quick work in progress or shares in the moment. Flickr becomes a place to share a larger collection of good solid work. My WordPress portfolio will, someday soon, be where I can show the things I really feel good about.

Maybe not crashing IS the hard part?


I wrote last week that I thought building the consumer interfaces and passenger experiences was the hard part of building autonomous cars. This week an article in The Information showed that even Google is having a tough time getting car tech just right.

According to the article the Waymo cars are subject to frequent sudden stops, presumably as their systems try to determine whether or not its safe to proceed. The author writes

The hesitation at the intersection is one of many flaws evident in Waymo’s technology, say five people with direct knowledge of the issues in Phoenix. More than a dozen local residents who frequently encounter one of the hundreds of Waymo test vehicles circulating in the area complained about sudden moves or stops. The company’s safety drivers—individuals who sit in the driver’s seat—regularly have to take control of the wheel to avoid a collision or potentially unsafe situation, the people said.

There are some simple reasons that you see a lot of autonomous car testing in California, Arizona and Nevada. Those those places are generally sunny, mostly flat and have cities with wide grid pattern streets. If you’re going to teach a computer to drive on public roads you don’t want to see if the sensors can handle looking down the crest of a hill, or dealing with roads and sensors covered with water, mud or snow.

I’m not here to pile on Waymo. Building autonomous cars is a really hard problem. I remain optimistic about the future of this technology. I’m just generally less willing to believe the hype that fleets of these vehicles, without safety drivers, are just around the corner.

It’s going to take time to train these systems properly and patience for those of us on the road manually driving to adapt to the AI reactions and expectations. As the article quoted

“It’s still a student driver, but it’s the best student driver out there,” said another person familiar with the Waymo program.