Eelco,
IMHO, what you describe here is 'flexible development' (I am avoiding
the term Agile) rather then reusability and maintainability.
Can you agree with this (somewhat condensed) assessment?
Erik.
Eelco Hillenius schreef:
> For both arguments: they *should care* about that and it should in
> fact be on the top of their list :). For the simple reason that it
> will save them money and effort.
>
> Don't view these two issues in very long, multi-project way per se
> though; any theoretical advantage you'll have after a year is probably
> YAGNI. But You'll reap the benefits of reusability and maintainability
> often in the same project. Typically projects run for many months -
> certainly so in big *slow* companies (usually years). You'll have
> people leaving and other people joining the project. When requirements
> change - and they do - you'll have refactorings. The better
> maintainable an application is, the less work and less error prone
> such refactorings will be. It will thus be cheaper and you'll be able
> to honor such change requests easier. Also, with projects of some
> size, you'll have variants of functionality (like a search function, a
> panel that displays information about the current context, etc).
> Rather than building all the variants over and over again, you create
> this reusable component and use it throughout your project.
>
> Eelco
>
--
Erik van Oosten
http://www.day-to-day-stuff.blogspot.com/
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
