Skip to main content

Keeping fit whilst sitting down all day

Media_httpnewsbbcimgc_cregw

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

Comments

Popular posts from this blog

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

Accessing the UI Thread with Tasks in F#

I have a Windows Forms program written in F# that can deploy a code base to n number of sites at once (you select the sites you would like to deploy to and it goes off and completes a number of tasks (backing up current sites, various unpacking and moving of files etc... ). Once you start it, it begins it's merry journey and begins to update the UI with what has happened. At the moment this method of updating the UI is not pretty because the threads I am doing the work on can't update the UI so I perform some fiendery to make that happen (don't ask). I knew there was a better way using some newer .NET features but I just hadn't got round to having a fiddle yet. I have now found that if you use the built in Task class but break your code up in a nicer way and then chain the tasks together you can then pass the correct context into the task that you want to talk to the UI. Here's a little script to give you a feel for it. You can press the "start" butt

NESTA - Next Gen.

via nesta.org.uk Following on from an article on the BBC about Raspberry Pi, this next gen report has some interesting findings. The scariest stat which I picked out from the BBC website was "out of the 28,767 teachers who were awarded Qualified Teacher Status... in 2010, only three qualified in computing or computing science as their primary qualification" Having worked as a computer science teacher for a year in a school that was a specialist in Computing I can concur that the uptake in Comp Sci was woeful. 2 Students for A2... The other teachers backgrounds in Computer Science was also fairly woeful (most knowing a bit about Office but still a paltry amount even about that). I couldn't speak for my counterpart that I was covering however. I suspect they were fairly up on things. All in all what kills me is that Computer science is not a secondary level subject. Areas are often covered, a little in IT, a little in DT subjects (if kids choose Systems and Contr