What is great software?

I overheard a conversation/argument a few days ago between two developers. At one point one of the developers said “well my product is greater than anything you’ve ever done!” It’s a shame the other developer didn’t respond by simply saying “prove it”.


How could the first developer prove it?


Proving whether a product is great or not depends upon how well the product fulfills its intended purpose. If a product was developed with the intention to annoy everybody who uses it, and it does, it’s a great product. If it doesn’t annoy the users, it’s not a great product. Of course, this would rarely be the intention for a product, but it illustrates a valuable point. A product doesn’t have to look good or work perfectly for it to be great, unless that was the intention

Comments

Post a Comment

Popular posts from this blog

All new developers should read this book

Image
I read this book a number of years ago when I was a junior developer in my first job. At the time I had about one years experience developing web applications (Classic ASP, JavaScript, CSS, and HTML) using knowledge I’d gained at University and anything I could find on the internet. Keen to keep up with the latest technologies our development department decided to use, the then newly released, Microsoft ASP.NET. To help smooth the transition, from Classic ASP to ASP.NET, we were sent on a “suitable” week-long training course. Eager to employ our newly acquired skills we returned from the course and went to work hacking together ASP.NET applications in the same, mostly non object-oriented, fashion. Soon after, a new senior developer joined our team and upon recognising my limited object-oriented approach, and complete lack of design pattern knowledge, suggested I read this book. I highly recommend this book if you have: Little or no object-oriented, or design pattern, knowledge. 
Read more

Requirements Change is not an excuse

When was the last time you developed a product and knew all, and I mean all, of the requirements, before you started implementation; never? That’s right, requirements change, they always change. If you’re developing a product, for yourself, and you’ve created your own requirements, chances are you’ll change what it’s required to do, whilst you’re actually developing it. This is only natural. As you spend more time on a project, you should gain a better understanding of what you’re trying to achieve and how best to achieve it. This holds true when the product requirements come from somebody else. Developers are often asked to develop a product, based on a set of loosely thought through requirements, only to find that the requirements change, when more thought is given to the idea (often as a result of the developer asking for more information because the original requirements don’t make sense). Because requirements always change, it is not reasonable to use this as an excuse for late
Read more

The Beginning

I've been a software developer for about 7 years. I've enjoyed it, mostly. I've learned a lot. I’ve worked pretty hard but I’ve never been one for working long hours. I value my   spare   time too much. I recently,  officially,   started a new role as a program manager. The role, actually, isn’t quite that clear cut (are they ever?) as it involves some line management responsibility also.     I’m going to use this space to document my thoughts on software development
Read more