Look I am not against methodologies, they are definitely a step in the right direction, but I think there is a mis-understanding of what the priority is in creating/using a methodology.
But we have to be using them for the right reasons, and prioritizing what's important in coding.
First off, the most important thing is:
1. Performance and Scalability, there can be no sacrifices made in this animals name. Simply if your methodology even takes 1 millisecond away, it's not worth it. Really, because it can so easily add up. Because without performance or scalibility, why are you even coding? Unless it's just for your own use?
2. Usability, can this methodology hurt/inhibit/enhance customer experience? Now my personal experiee in fuseboxed sites, is definitely yes! I hate fusebox url's, it may make sense to the coder, but i like having pages with distinct file names, that make it easy to understand where in the site I am.
3. Modularity, this is a big one, used as the catch phrase of methodologies, which method of modularity/code re-use do you use? Cfincludes, custom tags, cfcs, cffunction, udf, cfmodule? Remember priority one???
That's a big conflict, because seriously native cf, or cfincludes are top of the chart when it comes to speed and performance.
I am all for modularity/code reuse, as long as it doesn't hurt even by a nanosecond my performance or stability.
Because in this day and age of high traffic sites, and different new technologies competing for web application heaven, we must compete by only offering highly scalible, high performance, high available web apps/web sites.
Anything else, and we might as well not be coders.
It's drastic, If we want ColdFusion to be top dog, then we must stick to our guns to those top 3 rules, in that order!