Question on object oriented programming

Hi Chul,

I remember feeling like that too. My experience is that dividing related chunks of logic into classes comes with experience, continuous learning, and experimentation.

For work projects, I certainly try to have a conceptual "blueprint" of what I'm going to code, but it's rarely more detailed than a workflow on a whiteboard and a design pattern such as MVC (model-view-controller) or MVP (model-view-presentation) - assuming I'm writing an app. Outside of that, I don't really have any classes in mind. For my own side projects, the whiteboard workflow is usually in my head :P (not necessarily the best idea lol).

Based on my experience, I start to use classes when I see the same code being used in more than one place (I might put this code in something called a Util class). Or when when some logic is related so that it can be isolated into its own class.

All that to say, OOP (and coding in general) is an art/craft. There aren't very many definite right/wrong ways to do things, although some ways have pros/cons depending on what your goal is. Some of the above may seem hard to understand where you are right now - and that's completely understandable and to be expected. I was there too. The best answer to your question is to keep learning through googling, reading other people's code, watching Treehouse videos, and asking for code reviews. But, most importantly, in my opinion, you need to take those learnings and keep experimenting by writing more code :). In other words, be an active learner and put that learning into practice.

I hope that helps! Let me know if you have any more questions!

Keep it up :)!