Skip to main content

Imperfection

We need to embrace imperfection.

This doesn't mean we need to produce bad software.

I do not mean the classic software statements like "move fast and break things" or "if you are not embarrassed by your first release you've waited too long".

Rather, I mean imperfection in the results we achieve should be embraced.

What seems to actually happen is something along these lines:

  1. A business attempts to make a positive change and is public about that intention
  2. Some failure, compromise or other imperfection comes to light
  3. Society views this imperfection as worse than an similar (or even more terrible) imperfection in an organisation without the same good intentions

Now, we do need to hold ourselves and our organisations to account. But we also need to balance that with the fact that change on the social and environmental scale we need is going to be a messy road. We should avoid a "throwing the baby out with the bathwater" mentality.

About the author

Barry O'Kane

Barry is the founder of HappyPorch. With 20 years in the web development industry as a programmer and agency owner, he has a preternatural ability to decipher the systems and processes code that holds many teams back from achieving their goals. Partners say Barry gets to the root of issues quickly and makes it downright easy to deliver good work.    

While he's unbelievably grounded, it's not uncommon to find him sailing through the trees as he paraglides his way round the world.