Tuesday, October 11, 2005

Framework Translation/Conversion

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...

Monday, October 10, 2005

Intro To Fusebox

Well the day has finally come, I need and am going to take the intro fusebox class. It's not like I don't want to learn anything new, i just want to learn things that make me a better coder.

In this case it's more about getting skills that will get me a job.

Intro To Fusebox

I don't hate fusebox, as much as not really want to use it, because 100% of the time i'm a solo coder, working on hte full application.

I also don't like having all applications go thru a central app, which over time can tend to get bloated. That's how these things can get...

However there are some real pluses to fusebox, that I bet most of you thought i'd never say as long as I was alive...

1. Modularity - This is to be commended, and modularity used correctly, for maximum performance.
2. Teamwork Oriented Framework - I commend any method that helps new coders and old coders work together to create better products.
3. Standards, standards - I may not agree with all the standards of fusebox, but getting coders to stick to a standard instead of making one up, every week, is to be commeneded. This is a major problem in our industry.

Now as for OOP, I really don't care if other people use any model of thinking as long as it produces results, but then as long as i can produce results,why does it matter how i think of programming?

I have done plenty of javascript programming in my career, it is object oriented, and I can usually get done what i need to get done, without being a hardcore OOP.

For me the highest goal is creating solid applications we can be proud of, and not have to fix, upgrade because it wasn't done the right way the first time..

I also feel it's important we think about the posterity, if we died, how easy would it be for other people to fix, learn, change, any of the applications I created.

But when lots of people use lots of different ways, it creates havoc for other people who may have to change/alter their code.

Instead of making this a holy crusade for whichever framework or methodology or thinking process, we should concern ourselves with creating great applications, solid standards for our industry, and finding ways we can work together, instead of fighting..

I know i've had my share of flaming, but I'm done with that, let's move on, let's make ColdFusion the best web industry it can be...

I've been reading a lot of interesting stuff on fusebox, oop, and i no longer care about the flame wars, I just want to get a job, learn to master my craft.

And just keep moving forward...

Does anyone care to share their thoughts?