Jul 28 2014
Steven O’Grady is the co-founder of Redmonk, a developer-focused tech analyst firm, and a very smart analyst at that. I first got to know him in 2006 via my old boss at Lenovo, the CMO Deepak Advani who had a deep interest in Open Source and developer relations from his days at IBM. O’Grady and his co-founding partner James Governor gave us invaluable insights into the Open Source market, something that was unexpectedly crucial to Lenovo’s digital marketing focus as unbeknownst to us, one of the iconic Thinkpad laptops had been embraced as a reference platform to simplify hardware driver development for new distros.
Steven is also a great fan of all things Red Sox (his blog “Wicked Clevah” is one of the few I read) and is a striper fisherman up on the coast of Maine where he works and lives. So our orbits have overlapped on a few vectors.
This past spring he published with O’Reilly Media a very compelling argument that developers are the “new kingmakers” in contemporary IT and corporate digital strategy because of their crucial role in building value, defending against disruption, and making the technology decisions formerly reserved for procurement teams and the CIO. The result is a complete over-turning of the way organizations select and deploy technology, putting the developers in charge of the tools and standards that govern IT-enabled innovation and operations. We intuitively figured that out at Lenovo under the premise that when anyone makes a technology decision — “what phone should I buy? what laptop? what software?” — they turn to the most technical and expert person in their network. For those of us trying to build an influencer model online to sell computers, that audience was comprised of developers. Make them happy, give them what they need in terms of information and content, and they in turn will be the ones who declare if your technology is crap or not.
O’Grady nails the impact that the developer community is having on tech — from standards to commercial software to the way companies hire and retain the best coding talent they can find. His point is going to be very bleak new to the marketing teams at B2B tech companies. All those white papers and conferences and drive to get to the CEO and the COO and the CMO and the CIO ….. guess what? Developers could care less and they are the ones who matter.
“In the latter half of the 20th century, developers were effectively beholden to their employers. The tools they needed to be productive — hardware and software — just were not affordable on an individual basis. Developers wishing to build even something as trivial as a website were confronted by an unfortunate reality: most of the necessary building blocks were available only under commercial licenses. Operating systems, databases, web and application servers, and development tools all required money. To get anything done, developers needed someone to write checks for the tools they needed. That meant either raising the capital to buy the necessary pieces, or — more often — requesting that an employer or other third party purchase them on the developer’s behalf.
“The new century, however, has ushered in profound and permanent shifts in the relationship between developer and employer. No longer is the former at the mercy of the latter’s budget. With the cost of development down by an order of magnitude or mode, the throttle on developer creativity has been removed, setting the stage for a Cambrian explosion of projects.
“Four major disruptions drove this shift: open source, the cloud, the Internet, and seed-stage financing.”
Basically, the point is that the company may buy one set of technology but developers will be developers and build stuff with the tools they want to use, not the tools the CIO negotiated a good price for out on the golf course. Rather than put up with “official” technology, developers just get stuff done with the right tools — generally free tools — that get the job done.
“….the balance of power began to tilt in favor of developers. Developers, not their bosses, became the kingmakers. Technology selection increasingly wasn’t determined by committee or bake offs or who played golf with the CIO, but by what developers decided, on their own, to use.
“MySQL salespeople used to walk into businesses, for example, only to be told that they were wasting their time because the business wasn’t using any MySQL. At which point the MySQL salesperson would reply, “That’s interesting, because your organization has downloaded the package 5,000 times in the last two years.” This was and is the new balance of power. Not for every technology sector, of course, but for more every year.”
This is a very concise and accessible book — aimed at the marketers and executive management of companies who rely on developers to build their success. In my bookshelf of tech books that matter, this one will have a long shelf life. If you’re managing digital strategy, evaluating tech vendors, or trying to market hardware and software, this book can be digested in less than two hours and will, trust me, have an impact on how you see the new world.