R1D17 Nose Dive into OOP in C#

| programming | dotnet |

I worked through module two of the Object Oriented Progrmaming in C# course on edX.

One thing that is a bit confusing (and I am sure will come back to bite me in the ass later on) is how new classes are magically usable once they are created. i.e. unlike in python and java where you must import everything at the top of a file, once you add a class in Visual Studio is becomes immediately usable in order parts of the code without having to explicitely import it. This is handy, but also seems like it could create some issues in the long run in the sense that it is not immediately obvious which parts of the code are being used from one file to the next with these implicit imports.

It is not immediately clear to me, but I suspect that this is only true in the context of a namespace. It seems that C# allows you to “magically” use all members of a namespace without having to import them explicitly.

Abstract classes and abstract methods. You can create “sealed” classes which cannot be inherited. Interfaces are classes without implementation. I feel like a good analogy for this would be header files in C, C++ or Objective-C. An interface is really what an API refers to in a traditional sense (not like REST API). It is a “programming contract” that guarantees users of the implemented class that the functionality of that class will implement everything that is defined in the interface.

In the lab portion of the course we refactored our “school simulator” to have Students and Teachers inherit from a base class of Person.

Tomorrow I hope to wrap up the last module of the course which has to do with memory management and then move on to the last course of the series that deals with data structures and algorithms in C#.

 

 

Thank you for reading! Share your thoughts with me on bluesky, mastodon, or via email.

Check out some more stuff to read down below.

Most popular posts this month

Recent Favorite Blog Posts

This is a collection of the last 8 posts that I bookmarked.

Articles from blogs I follow around the net

Occupation and Preoccupation

Here’s Jony Ive in his Stripe interview: What we make stands testament to who we are. What we make describes our values. It describes our preoccupations. It describes beautiful succinctly our preoccupation. I’d never really noticed the connection between th…

via Jim Nielsen’s Blog July 17, 2025

What do we do when the facts don't matter?

As a journalist by training, I have what you might call an addiction to facts. I believe that there are things that are true and things that are not, and that we can determine one from the other through observation, rational thought, and meticulous resear…

via The Torment Nexus July 17, 2025

Back to the Future

This past weekend, I decided to take a trip down memory lane and take a look at the evolution of this blog’s design over the years (with a little help from the Wayback Machine). While I’ve really enjoyed the challenge of making an obsessively backwards co…

via flower.codes July 17, 2025

Generated by openring