There are many more Juiceros out there.

Like apparently everyone else on the internet today, I was reading the Bolt post on Medium describing their tear-down of Juicero's ridiculous juicing machine and the description of its spectacularly over-engineered internal components.

The interesting (to me, at least) part of the post was this bit toward the end:

Constraints during the earliest stages of a hardware company’s life force founders to carefully allocate resources to find creative solutions. I hope this post serves as a lesson to other hardware startups that spending tens of millions of dollars on product development prior to shipping a single unit is a goal that’s not worth striving for.

Let's broaden this point to the question of infrastructure in general…

Cloud providers and push-button provisioning eliminate the constraints of physical gear, but in doing so, do they also enable profligacy and poor/inefficient architecture?

Yes, we all know that Netflix has miraculously moved everything to AWS—mostly because Netflix can't stop talking about it—and the ever-accelerating commoditization of the general technology stack has made possible all sorts products and services that might previously never have seen the light of day.

Still, if unconstrained design can lead to a lovely but fragile and over-engineered contraption like the Juicero, does not that same risk plague any technology architecture where prior hardware constraints have been removed?

Show Comments