There’s a culture in the US called the maker culture, a hipster phenomenon. Related to the hacker culture, it represents a technology-based extension of the DIY culture that revels in the creation of new devices or systems.

I’ve been a maker for years. For me to feel like I’m accomplishing anything, I need to build physical things such as racing drones, motorcycles, books, on-demand video courses, and, yes, cloud-based software systems. If I don’t make things, I feel a bit empty and unfulfilled. I know there are many people out there who share this condition.

[ InfoWorld explains: What is multicloud? The next step in cloud computing. | Get started: Going multicloud? Avoid these 3 pitfalls. • Understand the multicloud management trade-off. | Keep up with the latest developments in cloud computing with InfoWorld’s Cloud Computing newsletter. ]

Being a maker involves taking some sort of risk. The risk of failure is the reason many nonmakers use to avoid building things or systems. Dare I say that nonmakers are typically holding leadership positions, typically supervising the makers? This has been the way it’s been for hundreds of years.

To read this article in full, please click here