Have you created a software Frankenstein? Though the intent of your creation may have been something beautiful, the positive aspects of the design are quickly overshadowed by glaring design issues. This ultimately results in an army of villagers (your customers) chasing you down with fire and pitchforks. Chad Kreimendahl explains how to get yourself out of this monstrous dilemma.
Amidst the alphabet soup of technical acronyms, API has been standing out recently. It has almost reached buzzword status. I think a lot of people have a vague idea that an API can be used to integrate data between applications, but what exactly is an API, and how are they used?
A few weeks ago I was able to do something that I hadn’t done since graduating college. I went on a vacation without my laptop and without my phone. I had my boss’s blessing and the support of my team. For an entire eight days, I was able to unplug. When I got back, things were just as I had left them. I didn’t have any fires to put out and no urgent business. Everything just worked the way it was supposed to. It wasn’t luck. It was designed that way.
If you’re an expert in your industry who’s designing a product or service, there’s a strong possibility that you’ve been a victim to this monster we call Design Hubris. Some of us are more susceptible than others, and the effects are almost always permanent, because they hit you early and they hit you deep. They spread like a virus, infecting all subsequent decisions and features.
At Onspring, we’ve spent much of our time and effort, both in product design and simply running our business, avoiding the “boogeymen” that disrupt so many forward-thinking companies. Running this gauntlet of ghouls has taught us many things, and the lessons of our former lives have frequently guided us when we might otherwise have wandered in the dark.