![]() That's not to say that I wouldn't benefit from some more object-based programming like a Service / API layer but, when it comes to the very data-centric style applications that I have built over the years, pure OOP doesn't really provide a huge benefit. For many of the applications that I have built, object oriented programming is simply not the best tool for the job. The most honest answer that I can give you is that I generally don't need it. ![]() So this begs the question: why do I even need object oriented programming? If what I am doing is working, then why bother changing it? In fact, I'd bet that many of the procedural-style web applications that I've built will go on to be used for years. And you know what? I don't think any of the applications have died horrible deaths. ![]() That means that I've spent the last 6 years building web applications with procedural code. I've been a web developer for a good 8 years and have been programming ColdFusion for about 6 and I am just now starting to get into OOP. The biggest hurdle that object oriented programming faces is the simple fact that many of us have been building successful procedural-style web applications for years. Last week, while covering the events at Hal Helms' "Real World OO" class, I had several inquiries, both direct and via my blog comments, asking what was the point of all of this was? How pure does object oriented programming need to be? What size does my project need to be in order to best leverage object oriented programming? I am very new to OOP, so I can't necessarily answer these all that well but, here is the best explanation / exploration of these topics that I can offer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |