Thoughts on learning OOP in Python

As I learn more about Data Science, one of the topics that have grabbed my attention is OOP (Object Oriented Programming). After learning and using various different types of built in classes and instance methods, before I even knew to call them that. The idea that I could make my own caught my imagination. The idea that I could tailor make classes and methods was an enticing prospect. I could already imagine having my own personal classes to help me with things that I had to do on a regular basis.

In my previous work, I had my keyboard completely setup with shortcuts for things I did often. To the point that when I was on other computers, not doing anything related to work, when I tried to type something or do something that I had programmed as a shortcut, I found myself automatically hitting my shortcut combinations. I then had to remind myself that I was not at my work computer. In addition to this, I had documents that were setup to be able to easily access for things I did less often, but often enough that I did not want to have to type them out each time.

Therefore I was very excited to able to do similar things in programming as well. That was until I started trying to make classes and having things continually break on me. I found making classes in Jupyter notebook much simpler as I could test each part of my code before putting it into a general class. However, I realized that as I was making classes that way, they felt very basic and not able to have the flexibility to do more general things under other circumstances outside the specific project I was working on.

I understood that what I needed to learn is the more ‘zoomed out’ outlook of creating classes separately. To be able to build them from a big picture standpoint where I could envision them being used in multiple circumstances. Not by building them for a specific code, in that case I could just use a function instead.

I also needed to learn how to build classes in .py files and test them properly at different points in the same way I am able to do in Jupyter. I wanted to get more practice using VS code, with the python debugger I had installed on it to help me figure out where my code could be breaking before even running it.

I feel I have gained a lot from this and a goal I have made for myself is to continue finding out more information about using OOP. I envision a time when I can have multiple classes that can help me with different tasks that I do on a regular and then even a semi-regular basis. I see this will take a lot of work to build so I will need to decide which processes are ones that are worthwhile to create classes for.

I feel like I have touched something that has endless possibilities for how to use it. I am looking forward to this journey of learning, with writing code, having it break and fixing it along the way.

With OOP it feels like the sky is the limit with how I can make code for myself to help with many things I may need to do in the future, both personally and for whomever I will be working for.

Related posts:

When Mayor Chokwe Antar Lumumba ran for mayor of Jackson, Mississippi, knocking on neighbor’s doors and talking in the fiery language of liberation to would-be voters, one practically minded resident…

Welcome to the ResumeInventor! Here is presenting the Sample New Fashion Designer Resume. This is a Fully customized Resume Template, With it, you can create/ design your profession-based resume…

Setelah tidak pernah menulis lagi, aku kembali dengan tulisan yang (seperti biasa) hanya berisi pertanyaan — pertanyaan yang tidak ada jawabannya. Atau mungkin kali ini lebih banyak kritik, entah…