Geeks With Blogs

News Dave's Mug View David Oliver's profile on LinkedIn Add to Technorati Favorites Blog Directory for Guildford, Surrey
Dave Oliver's Blog Enterprise Technology Thought Leadership in a FTSE 100

Now here is a real treat!

Bill Gibson one of the key Architects on the Whitehorse team has started blogging and his posts so far have been insightful as more background about Whitehorse has started to immerge. Bill’s blog can be found here.

So what is Whitehorse? Whitehorse is the Distributed System Designers in Visual Studio 2005, available in the Visual Studio Team Edition for Software Architects.  More info can be found here.

Whitehorse, the Distributed System Designer are not new ideas but it is the latest revolution (as in turn of the wheel) of this idea.

By reading recent interviews with Steve Cook it is apparent that Whitehorse (I prefer calling it that, had you guessed?) illustrates that this is the first step in a journey that theses guys want to take us.

With the inclusion of the forthcoming API, this will allow the community to let their imaginations go wild and I can see allsorts of DSL’s appearing which perhaps this is the point.

My concern is a general point of development culture, it’s pretty clear that application design is very much seen as the territory of the developer, the Architect gets to sort out the servers and infrastructure, heaven forbid that he/she should come of with not only a detailed design of an application but it’s code.

Tools in the past such as CASE have always been a bit rubbish as they promised so much and didn’t deliver. A lot of free thinking has evidently gone into Whitehorse and with the realisation that this is the first episode in the story that will only get bigger and better. With each new release, developers are going to soon realise that a cultural change is taking place as we try to abstract parts of the development code in perhaps a way that they aren’t familiar.

Obvious any change will generate resistance, but putting my developer hat on for a second I would advise developers to go with it as the end product will likely to be of a better quality as the guys with the big picture will be able to meet the guys at the coal face. Both sets will be able to see where each other is coming from. Also with the power of abstraction you will inevitably see more of the code you want to do and less of the stuff you don’t but this is a promise that has been issued so many times in the past, so what makes it different this time. Easy! Because it’s a common-sense fit.

Posted on Monday, October 17, 2005 1:33 PM Technical Architecture | Back to top


Comments on this post: Bill Gibson and Whitehorse

Comments are closed.
Comments have been closed on this topic.
Copyright © Dave Oliver | Powered by: GeeksWithBlogs.net