Object Oriented Debate Again…
So the Object Oriented Debate came up at work today… yet again. I’m a member of a six person team and only a couple of us have any experience with OOP, and then even less with regard to CFOOP (Coldfusion Object Oriented Programming). The old guard continue to be opposed to OOP breaking into our processes even though it has surely been the trend for Coldfusion since the release of MX.
I personally resisted OOP at first as I wondered if it really had a place in our section. We seemed to get by fine with our homegrown “frameworks” (if you can call it that), shared library of includes and user defined functions (written in cfscript) and good old fashioned spaghetti code.
However, over time I have felt compelled to take the plunge. So I’m working on applying OOP and Model-Glue to my next project.
Model-Glue is an object oriented Coldfusion framework that pretty much requires you to practice OOP in an MVC architecture. I’ve been using Fusebox for my last couple projects, which does have an OOP implimentation, however, I find Model-Glue a more “native” OOP framework. Fusebox 5 will support both approaches but I never could wrap my head around the OOP implimentation, possibly because I was use to the old 4.x style.
Anyway, I’ve decided to take the plunge and that means “sneaking” it into projects here at work. I’m finding that it isn’t something that yeilds quick returns, but in the long run, code is indeed more managable. But to get to the point of reaping a return on your investment, you must get beyond the initial learning curve, and also any barriers imposed by your team. It is really a question of “change management”. People often don’t like change especially if the benefits aren’t clear or immediate as is the situation with adoption of OOP.
Comments(0)