Universal standards could super-charge IoT growth, but can we get there?
The first remotely operated domestic machine — a toaster — was connected to the Internet less than a quarter-century ago, in 1990. The Internet of Things (IoT) doubled in size a year later with the addition of a coffee pot. Eventually, the Internet Engineering Task Force Network Working Group assigned the coffee pot its own specific standard, HTCPCP 1.0, the Hyper Text Coffee Pot Control Protocol, RFC 2324.
The Internet of Things has grown a bit since then, to somewhere between two billion and 10 billion devices, depending on who’s counting. But it could grow even faster, according to many of the biggest names in the global technology industry, if everyone would just agree on a universal set of technical standards.
The trillion-dollar question is, whose standards? Read more…
Everyone is racing to build the topmost layer for home automation.
Everyone’s racing to build the “god platform” for the Internet of Things: the highest, most generalized layer of intelligence and user interface that ties together connected devices and web services.
It’s tempting to look for analogy in mobile phone platforms, where Apple was initially dominant and now enjoys an extremely lucrative and influential minority position against Android. There are some crucial differences, though. For starters, adoption won’t be quite as easy; domestic appliances last for a long time, and nothing consumers have seen yet makes connected laundry seem appealing enough to justify early replacement of a washing machine. And even in cases where replacement is relatively easy, the grandest promises entail stitching everything into a seamless system — replacing just the easy stuff can seem pretty lame. Read more…
From the lure of work that matters to building your own device lab, here are key talks from Velocity New York 2014.
Practitioners and experts from the web operations and performance worlds came together in New York City this week for Velocity New York 2014. Below you’ll find a handful of keynotes and interviews from the event that we found particularly notable.
Mikey Dickerson: From Google to HealthCare.gov to the U.S. Digital Service
“These problems are fixable, these problems are important, but they require you to choose to work on them” — Mikey Dickerson looks back on what it took to fix HealthCare.gov and he reveals his reasons for joining the U.S. Digital Service.
A new partnership between O’Reilly and Databricks offers certification and training in Apache Spark.
Editor’s note: full disclosure — Ben is an advisor to Databricks.
I am pleased to announce a joint program between O’Reilly and Databricks to certify Spark developers. O’Reilly has long been interested in certification, and with this inaugural program, we believe we have the right combination — an ascendant framework and a partnership with the team behind the technology. The founding team of Databricks comprises members of the UC Berkeley AMPLab team that created Spark.
The certification exam will be offered at Strata events, through Databricks’ Spark Summits, and at training workshops run by Databricks and its partner companies. A variety of O’Reilly resources will accompany the certification program, including books, training days, and videos targeted at developers and companies interested in the Apache Spark ecosystem. Read more…
Camille Fournier on becoming a “multiplier” — and why multipliers are more effective than managers.
There are times when we all wish we could clone ourselves so we could get more done at work. In a Velocity New York 2014 keynote, Camille Fournier, CTO at Rent the Runway, presented an alternative, practical solution, that she argued is far more effective (not to mention feasible): become a “multiplier” rather than a manager.
Technical skills are important, she said, but they’re not ultimately the bottlenecks you experience later in your career — eventually, time and focus become the main hurdles. To overcome these hurdles, Fournier argued that you need to take a step beyond managing and focusing on creating additive value, and focus on multiplying your value by increasing the effectiveness of the people working around you.
Mikey Dickerson on why he moved from Google to the West Wing, and where we need to be allocating our engineering resources.
In a keynote address at Velocity New York 2014, Mikey Dickerson described his journey from working for Google to working in the West Wing of the White House, leading the US Digital Services group. He told the story of how a three-day review turned into a nine-week “herculean effort” by a team working 17 hours per day, 7 days per week to get HealthCare.gov up and running. The challenges, he stressed, boiled down to a few big, though basic, things — building a monitoring system, creating a war room to provide development direction and organization, and establishing a sense of urgency to get the problems fixed. “This very formidable obstacle, when you pushed on it even a little bit, fell apart; it was made out of sand,” he said. “Nothing we did was that hard; it was labor intensive, but it was not hard.”