Thank you, I had oped there would exist a sort document standardizing OOP code structure, or at least discussing various styles and their advantages and disadvantages, I guess I'll just stick to my own style then.

The Point and Car examples were disjointed and just illustrative of the fact that I don't really know where to stuff the functionality in my program since C# doesn't support freestanding functions, so this prompted me to ask myself what the "best" course of action is (that is, what style represents the OOP way the most).

Also, if you have 25-30 minutes I suggest you read this article by Bartosz Milewski. I found it quite interesting.

That's what I meant, OOP way. Can you point me to a resource that explains and defines what the OOP way is?

As /u/nefreat suggested the second snippets cater more to immutability and a later-stage translation of the code to F#, both are things that I like but since C# is based on the OOP paradigm I'd like to learn the "correct" way to develop OOP code.

Yes, I just finished playing around with Haskell for a small personal project and that's the exact same thing I thought about immutability. I learned to trust Haskell garbage collector, is C#'s comparable? In fact in the future I'll more than gladly learn F#, but I'm starting with C# because I also need to find a programming job relatively soon, and functional languages don't sell over here.

Thank you, I will check it out