As someone who is just making the transition to OOP in Python I totally agree with this post.
I started with PHP:
Learning programming syntax was really annoying
then learning loop and nested loop structures was hard
then learning a set of useful built in methods was hard
then learning how to interact with other systems was really hard
All the time I was learning this basic stuff I was writing code primarily for myself. I was the only one who maintained it and had to use it.
Now that I've moved over to python and I'm working on a code base that I expect to last, and will get to work with others on, OOP makes a huge amount of sense.
OO code may have more overhead to write (it does) but I find it much easier to read good OO code now that I understand the model, than I ever found procedural code even as I grew comfortable with writing it.
As a number of others have mentioned, OO code is about architecture and that seems to be what matters when you're trying to grok other peoples code. The specifics of how they did it only matter when you start debugging or optimizing. (In my limited experience to date)
I look forward to really getting OO, writing lots of code, and then starting to climb the functional programming mountain. But the poster is right, start bare bones, start simple, and build from there!
I started with PHP:
Learning programming syntax was really annoying then learning loop and nested loop structures was hard then learning a set of useful built in methods was hard then learning how to interact with other systems was really hard
All the time I was learning this basic stuff I was writing code primarily for myself. I was the only one who maintained it and had to use it.
Now that I've moved over to python and I'm working on a code base that I expect to last, and will get to work with others on, OOP makes a huge amount of sense.
OO code may have more overhead to write (it does) but I find it much easier to read good OO code now that I understand the model, than I ever found procedural code even as I grew comfortable with writing it.
As a number of others have mentioned, OO code is about architecture and that seems to be what matters when you're trying to grok other peoples code. The specifics of how they did it only matter when you start debugging or optimizing. (In my limited experience to date)
I look forward to really getting OO, writing lots of code, and then starting to climb the functional programming mountain. But the poster is right, start bare bones, start simple, and build from there!