http://www.codingthearchitecture.com/2007/06/08/premature_optimisation.html I'd like to talk to you about a sensitive subject that has been affecting me and, I suspect, affecting many of you as well. It's embarrassing so I'll say it first and you can all nod in agreement. "We're having problems on my project with being premature ... en Robert Annett Sat, 09 Jun 2007 13:35:07 GMT Pebble (http://pebble.sourceforge.net) http://backend.userland.com/rss http://www.codingthearchitecture.com/2007/06/08/premature_optimisation.html#comment1181595581469 Leaving non-functionals until the end of the project ... right ... this is why I'm keen on RUP style "executable reference architectures" that prove the key non-functionals as soon as possible. And it's also the same reason why I believe even "agile" projects need some form of architecture/architectural spike. I've been burnt by non-functional requirements before. ;-) Simon Brown http://www.codingthearchitecture.com/2007/06/08/premature_optimisation.html#comments http://www.codingthearchitecture.com/2007/06/08/premature_optimisation.html#comment1181595581469 Mon, 11 Jun 2007 20:59:41 GMT http://www.codingthearchitecture.com/2007/06/08/premature_optimisation.html#comment1181565512098 <p> I think I'm with Tom on this - "optimisation" can be a moot point before you've even written a line of code! </p> <p> "Tardy" optimisation is just as big a problem. The key, as you suggest, is probably to test early and test often to ensure you're neither too early or too late with your optimisation. And not to restrict your testing and optimisation to the build phase. </p> Kevin Seal http://www.codingthearchitecture.com/2007/06/08/premature_optimisation.html#comments http://www.codingthearchitecture.com/2007/06/08/premature_optimisation.html#comment1181565512098 Mon, 11 Jun 2007 12:38:32 GMT http://www.codingthearchitecture.com/2007/06/08/premature_optimisation.html#comment1181396107065 <p>It's funny, in my experience, developers tend to optimise too much. Architects too little... Developers will agonise over whether to use a String or a StringBuffer to save a few milliseconds. Meanwhile the Architect will stick the database on a server in Venezuela...</p> <p>Ok, I exaggerate, but I think as System Architects we are often guilty of leaving Non-Functionals to the end and then hoping for the best. The trouble is, clients always want to pay for the functionals and assume that 'good practice' will somehow magically take care of the non-functionals for free...</p> <p>Tom</p> Tom http://www.codingthearchitecture.com/2007/06/08/premature_optimisation.html#comments http://www.codingthearchitecture.com/2007/06/08/premature_optimisation.html#comment1181396107065 Sat, 09 Jun 2007 13:35:07 GMT