Re: always oop?

>To me, it doesn't seem like I need OOphp, but I'm new > to OO land. Should I use OO anyway? I'd say sure - why not? PHP won't hold you to it if you don't like it, and if you are new to it try it out. It's a different design process for sure, but if you use a lot of functions already it's kind of a natural progression. Also, even though you are _now_ the only programmer, and _currently_ are not planning on reusing any code, what happens if one of your solutions is fantastic? Why not save it and save time 3 projects from now? I am trying to make the same jump - and the more I do it, the nicer it gets. Key benefit: The planning process does not have to be done while at your computer - means that you can go out for coffee for half an hour thinking about what has to be done and cover it with "Planning is very important in the OOP paradigm" :)