In addition, there are times when the code is simple enough that throwing together a procedural script is faster and better than doing it object oriented.

Do you find yourself ever copying and pasting code from a previous project? Or do you rewrite code from another project? These are times that a reusable object may help. For example, my brother wrote a 3D engine object that would help him make 3D stuff in Flash for whatever project he is working on. You may want a reusable score keeper object or a connection object that regulated the data of two players so that they may play a game against each other.

I hope these may answer some of your questions. Good luck OOPing!

But 1 question (well several really, but…) is always at the back of my mind, When you are planning a project in OOP, do we think only about that project when writing ‘re-useable’ code, or do we also think about future projects that could ‘re-use’ the code?

The reason I ask is that most of my applications are small, bespoke and unique games. (I use game development as a way of testing new practices and ideas, I find games a good way to focus on planning, coding, UI, etc and all in a fun way with a useable product at the end.)

To learn OOP I am re-writing some of these games to integrate classes, but I am finding that the classes are only relevent to each game, so therefore I am wondering if I need to use them at all, when the 9 or 10 existing functions work the game fine?

I still want to put them into OOP just as a learning tool, but have you found a limit as to when OOP is needed and when not?