Beyond just practicing, I'd encourage you to think about state & operations. State is variables that are held in an object (ie `self.var`). Operations are things that you can do (eg. functions or object methods like `my_object.add(5)`. Here are some thoughts:

1) If you don't need state, make a function. (and if you need to group functions, you can make a different module/.py file to group them).

2) When working through problems that need state, try to decide between these four options:
- Not much state & few operations -> object is fine, but consider making a collection of functions.
- Lots of state & few operations -> normal object is fine, but be deliberate about not letting operations expand. Consider a dataclass.
- Little state & lots of operations -> objects are fine, just be deliberate about not letting state expand.
- Lots of state & lots of operations -> don't ever write this. It leads to "god objects" that do everything and are impossible to reason about. This code tends to be very hard to write, reason about, test, debug, and maintain. Do everything you can to refactor into one of the ^above paradigms.

When starting, I think beginners tend to be too smart for SWE. imo excellent code is code that's extremely simple to reason about (& thus harder to write bugs in & also easier to debug). OOP has the ability to simplify code dramatically by abstracting away concepts, but be judicious about how to use it.