I have a theory.
A web application will be at least 100% better if the developers who create it also actively use it.
It is akin to a meal prepared by an expert chef. The best chefs constantly sample their creations as they prepare a meal. When it is ready, they’ll serve it to their patrons and then sit down themselves to enjoy what they have lovingly created.
Like a chef, expert developers need to actively sample (test and use) their software while working on it, then sit down and consume their own code as a user would.
QA provided by testing experts definitely has its place – but I fear that sometimes developers (even good ones) miss significant opportunities to write better applications because they rely too heavily on testers / users to catch bugs and provide interface feedback. This reliance costs time – but even more significantly, we lose opportunities to improve the user experience because those who know how to change the code don’t take the time to actively engage and use the application. This lost opportunity for creative improvement could be avoided if developers spent an hour actively using the application for every 10 hours spent coding.
When I say using – I don’t mean quick tests, scripted testing, a little demo or anything like that – I mean actively using the application like their users will have to. I’m talking really, really use it and engage. A good chef will sit down and eat the meals he prepares – from that he draws inspiration for improvement. Programmers who consume the applications they write will create better software – hands down.
Topics:
