Skip to main content

Software Development Method acting

actor

I listened to the first part of .net rocks show 722 whilst out for my lunch. Dan North mentioned the excellent output of developers sitting with traders coding and pushing. To me this is one of the ultimate ways to achieve excellent software. I am a big fan of the idea of method acting as a software developer. I am pretty sure someone else has already coined the idea. 

Essentially I like the idea of sitting and working with the people I am going to write the software for. Working with them in their daily tasks as if I were a normal employee. It's how I started out coding. I worked in various jobs as an administrator, a construction estimator and many other roles. Initially with Excel and Access and then with VB.net and other tools I just wrote software that made my particular tasks and those of other people in the office easier. The code was outrageous but generally worked. When it didn't I could fix it easy enough, the person who had the problem told me there and then what was wrong and what they expected it to do. 

Sitting with people in this manner can help weedle out the features that the client doesn't even realise they need. I don't believe there is any greater method. Even asking them to do it front of you can cause a user to act as they think they should instead of how they actually work. Working with them builds up trust and a relationship that will help you all the way through the process. Think of the undercover boss idea.

There are problems associated with this obviously.. Your company loses a dev for a little time, and there is the question of paying for the developers time whilst this process is going on. For me the time saved afterwards in development and the strong understanding of the domain that will be gained pay for themselves.

Picture taken from http://www.inquisitr.com/164153/daniel-day-lewis-spotted-with-abe-lincoln-beard/

Comments

James Printer said…
The password is Burgers

Popular posts from this blog

Reigniting posterous again perhaps

I'm taking another look at Posterous again. I'm not really sure why as I haven't written a proper blog for a while but this seems an easy way to share between all my other tings...

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

Motorola MC65

We have a new PDA in town now. As a replacement for the army of MC9000 and MC70s that are in the field and are being discontinued, we now are moving up to the Motorola MC65. I have had the new handheld for about a week now and have been impressed so far. It's a great improvement over the MC70. I have no idea how the numbering system of the Symbol / Motorola devices works. I assume there must be several ranges such as the 50s 60s and 70s.? Anyway the?PDA?has windows mobile 6.5.3, a better touch screen and is faster. Much faster. The skin that has been put on the OS has also applied to our software and I think it makes it look much cooler. We had several problems in adjusting our software so it would work with the new MC65. First was the change in resolution. The MC70 has a much lower resolution than the MC65s and as some of our screens were not using the auto scale settings in the form and some of the buttons on our forms were created at run time rather than design time, this posed