Not so very long ago there was the debate around developer productivity, in the dim and distant past this was a really hot topic. Largely brought about by the development of High Level languages. Some of which are still with us and some have simply faded away.
The argument rested on the fact that High Level languages gave the developer a hand with the heavy lifting, great sequences of commands are condensed into a single line of code. The awfull relisation came about when researchers in Univac/Unisys examined the details and discovered a good programmer could produce a set number of tested lines of code in any language but it nearly always was the same number of lines.
This fact applied to Fortran, Cobol, Assembler, Basic, C, etc it was always the same.
If you then switch your attention to the most productive languages to write programs in you begin to see another story emerge. Easy to understand structrues and clear development rules around the language make a difference, but still its the number of lines.
This is where the PHP, ASP and ColdFusion debate really takes off, the origins of these three are similar, but the departure is around the vision PHP wants to be FREE, in both senses, ASP wants to lead on all fronts, ColdFusion wants to be Fast, again in both senses.
ColdFusion has retained this position over the last 6 years, both fast to develop and fast in runtime environments.
Adobe have continued where Macromedia left off, Macromedia gave us some great editing tools and FLASH now with Adobe we have a merger of the technologies.
Does Adobe promote these benefits? not obviously. The key issues are the TIME TO MARKET, miss XMAS and wait a year for your next chance, miss the sales season for holidays and miss a year. Speed of development is key where you have a time to market issue. Where the moment may be gone forever or certainly for a period.
Remember T5 well most of us will, and the trouble BA got themselves into, well this frequently happens with projects, they will come good in the end but not without taking a big bite out of your bottom line.
If you want to build in some contingency have a thought for the development team, if you get them the tools which give them productivity you can achieve with ColdFusion then you will have enough time to have a proper and complete test of your system. If you adopt an agile development methodology its even more likely you will keep ahead of the customers request for changes and still maintain a strong development schedule.
