About the Author

Hi, I’m Arantor.

I’ve been a website developer for at least a decade, and actively developing what could be called applications for probably half that time – and as part of that, learning the various ways that developers build things.

I write this blog about innovation with not only the desire to watch improvement amongst the fields that computing brings us, but out of a personal sense of frustration, having been part of various groups over the years that co-ordinate development, and realising that very few developments ever seek or strive to improve themselves or their work, but ultimately chase competition, without really watching any of the field truly innovate.

Maybe by looking at innovating instead of imitating, we can do things we couldn’t even conceive of before, because looking around us means we’re not looking ahead to what we can achieve – instead of looking at our peers, we should be looking at where we can get ourselves.

Some people believe that innovation is bad for competition – so I’ve been told, anyway. That if you innovate, you deviate from being able to be competitive, because if you’re deviating from what the competition is doing, you’re not competing. Or, at least, so I’ve been told.

If anything, the contrary is more true: innovation is the corner stone of competition – if you have nothing but the same as your competition, you have nothing to compete on. For a software package, for example, if all the packages in a field all have the same features, and nothing to compare them, the only comparisons can be drawn on things like support, or aesthetic feel, rather than which is the better tool for the job.

I think developers like myself should strive to make each tool be the best it can be – and to help users find the best tools for the job, which may or may not be the tools we produce – and in so doing, everyone is a winner, all because we refuse to stand still and accept what we have, and in so doing, we have innovation.