I’m doing a lot of re-organising at the moment. There are a lot of things going on within the business that means I have to think about what is happening, where and when. Those of you who know me personally know that I have given serious consideration to wrapping the business up and doing something else instead. Over the last week I’ve made some decisions.

Whilst this does not go into immediate effect, a new website will be coming online at vagueware.com in the next week (and the site currently there will find a new home announced at the same time) which will in effect take over from blog.vagueware.com (the one you’re reading now) which will remain in place, but is unlikely to be updated much in future.

I started out wanting to talk about ‘Innovation in Software’ here but quickly discovered two things:

1. Too much of it is happening to make meaningful sense of it all
2. Most of it is incredibly dull

Therefore, rather than let this site languish I want to move things onto something more useful, pertinent and direct.

Those of you taking the RSS feed via feedburner (as I’m sure you all are), will notice a change in the name and content, but you will not have to make any changes to subscriptions: I’ll move you across seamlessly.

So, what’s going to be on the new site? What is this new direction?

Vagueware’s core activity is essentially building web applications and helping other businesses build web applications.

Whilst Vagueware Ltd will (for now) remain the holding company for Kagtum and Fluxish, I have found myself in the position of offering consultancy around architecture, deployment, developer liaison and industry best practice. Some of my work has started to cross over into project management, business process delivery and some rather wishy-washy areas that most developers do not have to touch, or choose not to because they think these things are unimportant: the new site will be focused on building that business with articles that should help do what I find myself doing in real life, that is bridge the gap between business managers and developers.

Believe it or not, when you start looking at development decisions from the perspective of cash flow, shareholder security and board authority you become a better developer. Likewise when you look at business issues from the perspective of development resources, 3rd-party frameworks and test driven development, you become better at business. That’s the niche I now find myself in: explaining to both the other side’s position. It’s interesting work at times, and allows me to be part-coach, part-developer, part-consultant and part-entrepreneur all at the same time. I’m now doing this for two organisations regularly and am applying some of the lessons to my own business plans.

Now I plan to share those lessons.

Some of you will disappear, others will arrive. I just hope that in the long term this is a right turn.

What it does mean big-picture wise though is a decision has been made: I’m staying in the industry. For now. I’m not dumping development any time soon but I’m certainly finding other things to do that have made life a bit more interesting.