Now as I get closer to when I take this Fusebox class, and I keep hearing really interesting and different posts on frameworks, methodologies, I am kind of seeing a change what my real concerns with different coding methodologies instead of just my core emotions...
Really the problem was that we all code from different situations. Some of us code solo, some of us do agile partner coding, some of us do team coding, we all do it in different ways.
So then the bigger concern is how can the different situations work together well...
I think there should be a form of etiquette to help us work together better...
For example if your a web shoppe, your coding methodology should adapt itself to whatever coding methodology the client's code is in. Unless your the only people doing codework for them.
However most of the time, fore big companies, lots of different web shops have done code for them. So to all have different applications, created completely differently makes sense.
Sure you can introduce new methodologies or frameworks to your client but if they're not signed off on the latest method/framework then stick to their style.
We all like to code in different ways, or experiment but why are we experimenting with them at our clients expense?
Above are experiences I have seen at different client companies I have worked at. Where the outsourced code would be done in fusebox or cfc's and 99% of our code was still standard CFML.
Either then all code should be converted to X framework/metholodogy.
For example, at one company our checkout ecommerce code was outsourced to a web shop, and the result was a CFC and application that interfaced with that CFC. I am sure it was very interesting, but none of the rest of our site's code was in a CFC, and are CFC's always the best way to go?
We really need a multi-part solution:
1. What framework/metholodogy consisteny should we use for our clients? Do we use our favorites or use the clients? What if the people that work at the clients dislike your methodology?
2. When is a good time to introduce methodologies to clients? And when is it not a good tme?
3. Which kind of frameworks are best for which kind of applications? Surely there is a performance guideline both in terms of ease of setup, scalability, modularity, there has to be a measuring stick so we know which tool for which problem.
Because acting in the dark like we are isn't very healthy.
I want honest conversation, honest questions, I am here to help us be a better industry. If you just want to flame, please go elsewhere...