Tag: cloud computing

I’m enjoying Zucked by Roger McNamee more than I expected to. What’s useful about his account is the stress it places on the engineering capacity of startups. What makes cloud computing significant is not just enabling growth without major capital investment in infrastructure, but also “eliminating what had previously been a very costly and time-consuming process of upgrading individual PCs and servers“ (loc 674). What makes open source software significant is not just the reduced costs of free of the self components, but the time saved when everything can be built on open source stacks. I’d tended to see these things as a matter of reduced costs and increasing flexibility, without grasping their significance for how limited resources could be deployed within the firm.

Both mean that the engineer capacity of a startup can be directed mainly at the “the valuable functionality of their app, rather than building infrastructure from the ground up“ (loc 660). This led to the lean start up model and the capacity to go live then iterate in response to what happens. Without this modus operandi and the infrastructure supporting it, would the harvesting and use of what Zuboff calls behavioural surplus have even able to happen? A little earlier he frames this in terms of an epochal shift in the engineering constraints which tech startups had been subject to:

For the fifty years before 2000, Silicon Valley operated in a world of tight engineering constraints. Engineers never had enough processing power, memory, storage, or bandwidth to do what customers wanted, so they had to make trade-offs. Engineering and software programming in that era rewarded skill and experience. The best engineers and programmers were artists. Just as Facebook came along, however, processing power, memory, storage, and bandwidth went from being engineering limits to turbochargers of growth. The technology industry changed dramatically in less than a decade, but in ways few people recognized. What happened with Facebook and the other internet platforms could not have happened in prior generations of technology.

Under these conditions, it’s much easier to experiment and it’s easier to fail. As he points out, Facebook’s infamous motto Move Fast and Break Things is emblematic of the freedom which decreasing engineer constraints offers for a nascent firm. But what does this mean culturally? I think this is a crucial question to explore both in terms of the firm itself but also the expectation which investors then have of what constitutes adequate growth for a lean startup?

To what extent does the obsessive drive for increased user engagement have its origins in the changing expectations of investors and the challenge of meeting them?  McNamee observes it makes investors more inclined to identify what they perceive as losers and kill the startup before it uses too much money. The rewards on offer for successes are so immense that many failures can be tolerated if they lead to one success.

It also makes it much less onerous for the firm to scale, with important consequences for a nascent corporate culture. Inexperienced staff can be a plus under these circumstances, as long as they have the relevant technical skills. McNamee argues that the success of Facebook’s staffing policy had a big impact on human resources culture in Silicon Valley.

From Zizek’s Trouble in Paradise, pg 57. This isn’t necessarily the case but it’s a claim that holds true in the absence of personal tech skills and a disposition to  exercise then:

The paradox is that, the more the small item (smartphone or iPod) I hold in my hand is personalized, easy to use, ‘transparent’ in its functioning, the more the entire set-up has to rely on the work being done elsewhere, in a vast circuit of machines which coordinate the user’s experience. The more our experience is non-alienated, spontaneous, transparent, the more it is regulated and controlled by the invisible network of state agencies and large private companies that follow their secret agendas.