|
John Kuhn wrote:
Is it possible to start an iterative development process by starting with Maintainability?
It is definately possible. My favourite way is by doing test-first (or test-driven) development. If you haven't tried it yet, my recommendation is that you do. If you have ever been involved in a project lasting for more that a year and have seen the problems that arise, you will soon be blessed.
|
|
|
|
|
Do you think that test-driven development alone can ensure maintainabilty? Isn't it possible to produce code that, while passing through unit tests, etc., is still not intrinsically maintainable? As I suggested elsewhere in this thread, maintainability is a design goal and a good coding practice, but it is not the principal aim of developing a particular system, is it?
What a piece of work is man, how noble in reason, how infinite in faculties, in form and moving how express and admirable . . . and yet to me, what is this quintessence of dust? -- Hamlet, Act II, Scene ii.
|
|
|
|
|
John Kuhn wrote:
Do you think that test-driven development alone can ensure maintainabilty?
If you are using TDD the way it is supposed to, then it is my beleif that you will automatically end up with code that is easy to maintain. If it's not, then you'll do some refactoring until it is. Your tests will tell you that all things are working fine dispite of the changes. Refactoring is a natural part of TDD and if you have complicated code then TDD says that you should (not may) make it simpler.
I'm not saying that other options are not important. If you want to sell your application it better be easy to use! But as mentioned by someone else in this forum, if you have code that is easy to maintain you can easily accomplish all other things on that list of options. But if it's not easy to maintain you'd better do all other things on the list correct from the beginning.
|
|
|
|
|
I suppose that we will have to agree to disagree; not that I think testing is irrelevant, or that maintainability is not incredibly important; on the contrary, they both play an important role in my daily work.
However, that you will "automatically end up with code that is easy to maintain" seems like a leap of faith. Maintainability exists at many levels throughout the project life-cycle, and has as much to do with code comments, coding style, and testing (the role of the individual coder and his or her work habits) as it does with a high-level perspective on systemic design issues and the interaction between components of a system (the role of an architect).
Overall, it is my true belief that the latter of these two, good system architecture or design, is the most important factor, since everything else follows from that.
(Please also note that my earlier line of making small assertions, followed by a series of queries was somewhat disingenuous; I was simply trying to provoke a discussion, in which I succeeded, since we are still talking about these issues nearly a week and a half later.)
What a piece of work is man, how noble in reason, how infinite in faculties, in form and moving how express and admirable . . . and yet to me, what is this quintessence of dust? -- Hamlet, Act II, Scene ii.
|
|
|
|
|
But by the time any serious maintenance needs to be done you'll long gone, so why bother with maintainability... thats some other poor suckers problem.
|
|
|
|
|
You must have been fired from every company I've ever worked for.
What a piece of work is man, how noble in reason, how infinite in faculties, in form and moving how express and admirable . . . and yet to me, what is this quintessence of dust? -- Hamlet, Act II, Scene ii.
|
|
|
|
|
Software Zen: delete this;
|
|
|
|
|
Although I think that ease-of-use should follow from good looking UI.
What a piece of work is man, how noble in reason, how infinite in faculties, in form and moving how express and admirable . . . and yet to me, what is this quintessence of dust? -- Hamlet, Act II, Scene ii.
|
|
|
|
|
How so? Good looking means "pretty", and it has nothing to do with usability.
|
|
|
|
|
It depends on your universe of discourse; in this case, we're talking about desktop applications. In this context, is it not true that when someone says "good-looking UI", they are usually referring to one that is clean, neat and well-designed? Is is not also true then, that those kinds of user interfaces are intrinsically easy to use?
What a piece of work is man, how noble in reason, how infinite in faculties, in form and moving how express and admirable . . . and yet to me, what is this quintessence of dust? -- Hamlet, Act II, Scene ii.
|
|
|
|
|
John Kuhn wrote:
In this context, is it not true that when someone says "good-looking UI", they are usually referring to one that is clean, neat and well-designed? Is is not also true then, that those kinds of user interfaces are intrinsically easy to use?
I'd agree with you there John. I yo-yo'd between easy-of-use and good-looking UI before choosing the latter; a good looking UI (by my standards) is an easy-to-use UI!
Cheers,
Paul
|
|
|
|
|
John Kuhn wrote:
Although I think that ease-of-use should follow from good looking UI.
Ummmm - not at all, no sirree, uh-uh, dead wrong, sorry, next contestant please.
It's true that butt-ugly UI's can't be easy to use, but fuufy "graphics uber alles" Uis can be harder to use than anything.
|
|
|
|
|
Perhaps a good-looking UI needs to be more narrowly defined. As you state, poor UI design can be difficult to use; but a good-looking UI is not necessarily an extremely graphical UI, either. There are, of course, many web sites that fall into this category: visually pleasing, but nearly impossible to decipher as a user interface. On that point, perhaps those should be counted as "Graphic Art" and not "User Interface" -- for is it not true that the words "Good Looking UI" imply that it is an interface designed for users? And, if so, wouldn't a "Good Looking UI" be intrinsically useful? Take for example the Windows Media Player. Is it not good looking? And does its simple, good-looking interface not benefit ease of use?
What a piece of work is man, how noble in reason, how infinite in faculties, in form and moving how express and admirable . . . and yet to me, what is this quintessence of dust? -- Hamlet, Act II, Scene ii.
|
|
|
|
|
John Kuhn wrote:
Take for example the Windows Media Player. Is it not good looking? And does its simple, good-looking interface not benefit ease of use?
Windows Media Player is an example of simple, good-looking interfaces falling short on ease of use. When I started with Windows Media Player, I tried to open a music file. There was no Open File, just an Open Location. I clicked that and got a dialog to open a web location with no browse button. I did finally got the music to play by opening windows explorer and double clicking on the file, but I was annoyed that I had to do it. To be easy to use, a program should provide the options that people are used to having and in the places that they are used to looking for them.
Nathan Holt
|
|
|
|
|
Are we both referring to Windows Media Player 9? Perhaps you should switch to compact mode.
Even in "full" mode, you have basic controls that you would have on a portable MP3 player or walkman, everything discloses its own function with tooltips, there's online help... Not that I think WMP is the best software ever for multimedia, but it covers the bases.
But then again, that's just my opinion, I could be wrong.
What a piece of work is man, how noble in reason, how infinite in faculties, in form and moving how express and admirable . . . and yet to me, what is this quintessence of dust? -- Hamlet, Act II, Scene ii.
|
|
|
|
|
For what it's worth, I think it was versio 6 or 7. I didn't look at the version, but I remember it was a year or two ago.
Nathan Holt
|
|
|
|
|
oh well.
What a piece of work is man, how noble in reason, how infinite in faculties, in form and moving how express and admirable . . . and yet to me, what is this quintessence of dust? -- Hamlet, Act II, Scene ii.
|
|
|
|
|
Think of a woman. More often than not the prettiest ones are the hardest to use.
regards,
Paul Watson
Bluegrass
South Africa
Christopher Duncan quoted:
"...that would require my explaining Einstein's Fear of Relatives"
Crikey! ain't life grand?
Einstein says...
|
|
|
|
|
Paul Watson wrote:
Think of a woman. More often than not the prettiest ones are the hardest to use.
|
|
|
|
|
Paul Watson wrote:
Think of a woman. More often than not the prettiest ones are the hardest to use.
Or, the best looking ones tend to be the most expensive.
Remember, even if you win the rat race, you're still a rat.
|
|
|
|
|
Yes, especially since everyone else is trying to use them too.
Regards,
Alvaro
Give a man a fish, he owes you one fish. Teach a man to fish, you give up your monopoly on fisheries.
|
|
|
|
|
I can't argue with that... I just hope my wife doesn't find this post.
What a piece of work is man, how noble in reason, how infinite in faculties, in form and moving how express and admirable . . . and yet to me, what is this quintessence of dust? -- Hamlet, Act II, Scene ii.
|
|
|
|
|
This poll would be a lot better if the user was forced to rank those choices in order of importance. The way things are going right now everyone's going to put #1 for all 6 options!
Joel Holdsworth
|
|
|
|
|
I did take the time to rank them, though having 7 factors and only 5 levels of importance required doubling up a bit. Oh well...
Will Build Nuclear Missile For Food - No Target Too Small
|
|
|
|
|
I screwed up. It was meant to be a single choice, not a rating choice.
Sorry everyone. All votes have been reset.
cheers,
Chris Maunder
|
|
|
|
|