> 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?
Sure, whatever works for you :) What I tried to get across is that I don't think reusability and maintainability have to be viewed as long-term things only. I know from experience they typically are viewed like that by managers, who'll say they won't need it as they rather get the project done. But writing maintainable and reusable code may save you or your colleagues trouble next week rather than next year. Projects without much discipline when it comes to avoiding copy paste code and such, move fast in the first two months and get bogged down after six. My experience with projects done with MVC frameworks is exactly that. The further they progressed, and the more complex the UI got (often projects start out solving the easy problems first), the harder it got to implement changes to the UI, get new programmers to work on the project, etc. When I started looking for alternatives some 3 years ago, I was primarily doing that for 'management' reasons. Eelco ------------------------------------------------------------------------- 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
