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
22 January 2012 at 18:47
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