• Are Humans Bad Drivers?

    Are Humans Bad Drivers?

    Whenever self-driving are discussed, almost everyone — the media, tech podcasts, twitter, your uncle — universally asserts that “humans are bad drivers,” usually adding something to the affect of “we need machines to save us from ourselves.” As a contrarian through and through, foregone conclusions like that immediately trigger my gag reflex.

    I don’t think humans are bad drivers and I more importantly I don’t agree with the tone of the conversation.

    It is true that Google’s autonomous vehicle programs has an incredible safety record, having driven 1.6 million kilometres and only caused 12 minor accidents. However, those statistics alone don’t paint the entire picture.

    To compare the raw driving abilities of robots vs humans, you have to level the playing field. Looking at the entirety of driving statistics, compared to the entirety of Google’s testing is not at all level. Google’s cars are driving under ideal road conditions (they can’t handle rain or snow), with precise GPS based instructions, on nice roads, in a well-maintained car.

    In order to compare the safety records of humans and robots, you would have to at the very least rule out all collisions that occurred under less than ideal driving conditions, with improperly maintained cars, on bad roads, by drivers not following GPS, etc. You should probably also rule out all collisions caused by inexperienced, since robots have perfect knowledge of driving rules and car physics. Given a level playing field against the current state of robotics, I suspect an random sampling of human-Americans driving the equivalent to Google’s fleet would result in similar safety statistics. I could be wrong, but I’ve never heard of a study comparing these factors.

    It is the soft skills surrounding driving that humans are less than perfect terrible at. A short list of things that we are bad at:

    • staying awake for long periods of time
    • staying focused
    • reaction time
    • stopping themselves from driving too drunk
    • driving for the road conditions
    • following traffic at appropriate distances
    • etc, etc.

    By removing the human element from the equation, a whole slew of potentially dangerous activities can be eliminated from the roadways. Case closed.

    Except, this changes the fundamental question from “are robots better drivers than humans,” to a question of human fallibility versus software fallibility, ie. does software make a fatal mistake more or less often than a human.

    While I believe this is at least in part what the manufacturers are trying to determine with real world road test. The scale of these test is much much too small. According to the US Federal Highways Administration, Americans drive an average of 341,000 miles per hour! Meaning, every 3 hours Americans drive as many miles as the entirety of miles Google has logged to date. The level of software reliability required for the scale of the US driving machine is orders of magnitude greater than what has been tested to date. Is software in other mass install bases this reliable? How many blue screens of death per hour does the world receive in aggregate?

    The world where robots are better at driving than humans, under a variety of conditions, en masse, seems like a long way away. I think that everyone from Joe Q Public to knowledgable tech pundits are drastically under-estimating the difficulty of this problem.

    More importantly thought, statements like “humans are bad drivers that need to be replaced by robots” expresses a human inferiority complex that is completely unfounded in 2016. If we’re going to go around saying shit like this, the robot overlords have already won.

     


  • Do we need an IMDB for websites?

    Do we need an IMDB for websites? Over the course of my 15 year career as a web developer, I’ve had a hand in dozens (maybe hundreds) of websites. A handful of the top sites I’ve worked on are seen by millions of people; and much like the clapper loader, child wrangler or caterer on a big budget Hollywood film, no one would be the wiser.

    Unlike an obscure Hollywood professional, the behind-the-scenes work of a web developer is rarely credited anywhere. Occasionally, our names will be buried on an “about us” or “team” page no one ever visits, sometimes we’ll leave fingerprints in an HTML comment. But the fact that’s there’s no generally recognized method for crediting the hard work that goes into web development (or other creative professions for that matter)… is a little weird and disheartening.

    For coders — who don’t have pretty pictures and mockups to post in a fancy shiny portfolio — the de facto industry standard for building reputation and gaining attribution seems to be a github profile. In theory github can be a low friction source to evaluate the work of a potential hire. However, in practice there are many reasons an excellent, experienced developer might have a sparse github profile. For starters, github profiles are public and paid work is usually the intellectual property of the client paying for it, not open for public posting. Secondly, coming up with unique ideas for projects, or extra free time to contribute to existing projects can be a daunting task for a developer who’s busy balancing hobby projects against paying bills and having a life. A sparse github presence should not be seen as an indication of… anything, really.

    The IMDB Model

    IMDB has a lot of features, some of which might or might not make sense for website listings: user ratings, trivia, things like design and feature history, etc could be interesting for larger well known sites. But the feature I’m most interested in for the purposes of attribution is the “cast and crew” listings.

    Essentially, listing every “crew” member of a web team would be a great way to present the type of recognition that I believe people in the industry deserve.

    Potentially, more importantly though would be the ability to reference an individual across all the projects they’ve ever worked. On IMDB when you click through to a crew member’s profile you can quickly see all the projects they’ve ever been a part of. This could give employers and colleagues a unique view into someone’s body of work and career progression. A listing like this could fill the gaps between a resume and a github profile. If it works for Hollywood, I don’t see why it wouldn’t work for Silicon Valley.

    Humans.txt

    In 2011, an organization formed to promote the idea of a included a humans.txt file with all websites.

    It’s an initiative for knowing the people behind a website. It’s a TXT file that contains information about the different people who have contributed to building the website.

    I recall some minor buzz around this initiative and it looks like they had aspiration to make it a W3C standard. But the buzz seems to have died off very quickly, their website hasn’t changed much since mid-2011.

    Humans.txt is the ideal vehicle for the type of information an “IMDB for websites” would need to know about the development team. The service could use humans.txt as a starting point to validate a website, then parse the file itself to suck in data for the listing. From there, unique individuals could be cross referenced using their twitter profile.

    That’s it

    I’m sure there are a tonne of challenges, as well as interesting directions and potential features, etc…this is admittedly not a fully formed idea.

    What do you think?

    (crossposted to medium)


  • Hei Opera!

    Hei Opera!

    Opera was the first web browser I truly loved. In the early days of the modern web, when we had 4 or 5 real legit competitors in the browser space, Opera was truly innovative. In the year 2000 it was the first browser to support tabbed browsing  (2 years before Mozilla, 3 years before Safari and 6 years before Internet Explorer!). It was also the first browser to implement a built-in pop-up blocker around the same time. Mouse gestures may have been my favourite feature of Opera back in the day. You could to navigate the web by drawing shapes with your mouse (“J” for back, “L” for forward). Might sounds a little silly in 2016, but in the early 2000s multi-button mice were not common-place and OS supported trackpad gestures were unheard of.

    I can’t recall exactly how long I used Opera or when and why I left. I suspect it was around the time that Mozilla’s Phoenix became the shiny new Firefox.

    Over the past few weeks Opera has been making some small ripples in the tech press. Opera is doing a few related interesting things. So I thought I’d give it a try again after all these years.

    For the past two weeks, Opera has been my primary browser on desktop, I’ve also tried out their iOS browser and free VPN.

    Briefly on the mobile experiences.

    Opera Mini is fine. iOS browsers are somewhat limited by being forced to use Apple’s rendering engine, so I wasn’t really expecting much. Opera mini has a “turbo” boost feature. By routing media request through an Opera system, image and video file sizes and be optimizes, improving page load times. I can’t say that I noticed the feature. However I’m not a heavy mobile browser user.

    Opera’s free mobile VPN (with build-in ad blocking) is a great step in the right direction, public wifi (especially in hotels) is sketchy AF! I had the prefect opportunity to test this out on a 5 day vacation last week. Unfortunately, it fell short, the internet was slower and my battery drained faster with the VPN enabled. I don’t know if Opera’s technology it to blame, if it’s just the nature of VPNs in general, or even if it might be my perception. I turned it off entirely after 1 day of usage.


    My desktop experience on the other hand, has been great!

    Opera dropped their own proprietary rendering engine in 2013, in favour of Google’s WebKit variant, Chorium. This means the developers tools, browser extension support and overall rendering is identical to Chrome. And this is a good thing!

    Screen Shot 2016-05-22 at 8.08.28 PMUsing Chorium as a platform to build on allows Opera to focus on adding features. For now, their main feature is built-in ad block. It’s good, quite good. It’s not configurable like a dedicated ad block extension, but it get’s the job done.

    Opera also plans to release their free VPN solution for the desktop browser. I’m not sure when I’d use this (my desktop sits behind a network I trust), but this is something you’re unlikely to ever see from Google, Microsoft or Apple.

    Overall, Opera is great and I think I’ll continue to use it as my daily driver.

    Give it a shot, if only for the nostalgia.