Beautiful sentiment, *if* you didn't inherit a 3500 template legacy application originally written on CF 4.
Both (comments and TDD) have their place. Fact is, what is simple and clear and second nature for me is Greek to a noob, and I train those all of the time. Comments are for those who come behind, remembering that not all of them share my level of skill (or my preconceptions of what is right and wrong to do). Steve 'Cutter' Blades Adobe Community Professional Adobe Certified Expert Advanced Macromedia ColdFusion MX 7 Developer ____________ http://cutterscrossing.com Co-Author "Learning Ext JS 3.2" Packt Publishing 2010 https://www.packtpub.com/learning-ext-js-3-2-for-building-dynamic-desktop-style-user-interfaces/book "The best way to predict the future is to help create it" On 2/28/2012 8:36 PM, James Holmes wrote: > Those using comments to plan code probably don't have any tests. Tests are > essential to allow re-factoring with confidence; comments don't provide > that benefit. This is not a religious belief, it's something that can be > demonstrated the first time you want to maintain a 1500 line file and all > you have are comments. > > In TDD, the test is written first. It expresses the design for the code to > follow. When the code is then re-factored, it ensures the code still meets > the original design. > > -- > Shu Ha Ri: Agile and .NET blog > http://www.bifrost.com.au/ > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:350159 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
