Skip to main content

Keeping fit whilst sitting down all day

Media_httpnewsbbcimgc_cregw
via bbc.co.uk

Obviously this is the eternal problem of the office worker. As a developer I am sit down almost all of the time as I am straight back on the computer at night until around 12pm most nights.

Whilst novel I think the treadmill idea is obviously no more than an amusement. The dream for me is to have a much more interactive environment to develop software in. It would be nice if you could stand and move virtual components around or build software using virtual components instead of just sitting down and typing. Obviously this would need some sort of higher generation language where more of the problems are abstracted out. It would be interesting if you could build classes like that, then bring up a virtual keyboard or use voice recognition to describe what you want to happen.

I can imagine this working brilliantly whilst pair programming. Two people creating tests, assumptions and building software in a fashion that is almost like a debate crossed with a squash match.

Whilst we aren't as close as I would hope, I don't think we are a million miles away from something like this when you take into account technologies like the kinect and the immersion ideas that Microsoft research are banding about.

[youtube http://www.youtube.com/watch?v=re1EatGRV0w?wmode=transparent]

One can only hope that this comes before I become so unfit and large that I turn into a Pearl like creature.
https://dl.dropbox.com/u/1041315/Pearl.JPG

Labels:

Comments

Post a Comment

Popular posts from this blog

Creating star ratings in HTML and Javascript

I'd searched around a little for some shortcuts to help in doing this but I couldn't find anything satisfactory that included the ability to pull the rating off again for saving. I'd ended up coming up with this rather cheeky solution. Hopefully it helps you too! This is my first post in a while (I stopped blogging properly about 8 years ago!) It's strange coming back to it. Blogger feels very crusty and old by todays standards too.
Post a Comment
Read more

Make your objects immutable by default

More about the Good Dojo In my post last week , I discussed creating objects that are instantiated safely. Please go back and read if you are interested. At the end of the post, I mentioned that I'd also written the class so it was immutable when instantiated. This is important!!! I feel like a broken record in repeating this but I am sure at the time of writing your code, you aren't modifying your object all over the place and so are safe in the belief that protecting against mutability is overkill. Please remember though, your code could be around for a hell of a long time. You aren't writing your code for now... you are writing for the next fool that comes along (including you) . Nothing is more upsetting that coming back to fix a bug on some wonderfully crafted code to say "Who has butchered my code?!", but often you were involved at the start of the process. You made the code easy to modify, allowing objects to be used / reused / modified without thi
Post a Comment
Read more

An instantiated object should be "ok"

I've been QA'ing quite a bit of work recently and one common theme I've noticed across both Java and C# projects I have been looking at is that we occasionally open ourselves up unessacarily to Exceptions by the way objects are being created. My general rule of thumb (which I have seen mentioned in a Pluralsight video recently but also always re-iterate in various Robust Software talks I have done) is that you shouldn't be able to create an object and then call a method or access a property that then throws an exception. At worst, it should return null (I'm not going to moan about that now). I've created an example below. We have two Dojos, one is good and one is bad. The bad dojo looks very familiar though. It's a little class written in the style that seems often encouraged. In fact, many classes start life as something like this. Then as years go on, you and other colleagues add more features to the class and it's instantiation becomes a second
Post a Comment
Read more