top of page

Object-Oriented Programming: Encapsulation


URL: https://www.codingblocks.net/podcast/episode-23-back-to-basics-encapsulation-for-object-oriented-programming/

I chose a podcast for my first blog post, and the reason for that is because I find podcast the easiest for me to understand and the most interesting. While there are many great blogs, books, articles, etc., sometimes I have a hard time following along and understanding completely what is being said. With podcasts, they are usually less formal and more ‘user friendly’. So the podcast that I thought to start off was with a very simple subject. After we had gone over some words in class a couple weeks ago, I felt like i needed to brush up on the programming terms, i.e why I chose a podcast all about encapsulation for object oriented programming. This podcast consisted of three men, who wanted to get “back to the basics” and get a refresh on the basic fundamentals. Now for a quick summary of what they talked about, it was legitimately all about encapsulation, and how it is portrayed throughout the different languages, specifically java, c# & java-script. They mention in each of these what is it and why it matters. So their basic definition was “Bundling your stuff up that only affects your scope so that people don’t have access to everything you do”. What they meant by that was what does the coder want people to actually see that they can interact with. Then they go in depth of the different kinds. The three main being Public, Private and Protected which is used for both Java & c#. Public is “the process of hiding internal implementation of the coders data and only exposing behaviors and properties that are wanted to interact with the people”. It is available to anyone that links that coders library and is the most open. Private is only available to those particular things that are in the class and are only to be seen by the members of the class that the coder is in. Protected is “anything that is in that particular class or is an inherited subclass of it and can use and access that same variable”. Then they also mentioned Internal, which is part of c#, which are “classes inside one’s assembly, DLL, EXE, etc, and those that can talk to one’s class but nothing else outside”. After explaining all the different kinds, they went on to mention the importance of encapsulation and having global variables is never good. Having global variables mean that

anything can be accessed and modified in any shape or form and many things can go wrong from having them. The importance of encapsulation is really stated and that they not only protect the application, but guarantee certain enter and exit points within it. Lastly, they mention others like protected internal, private protected and seal and encapsulation in java script. Overall, this podcast was a really good start to the many blogs, articles, podcasts, etc. that I will be viewing/ reading and talking about. It was very easy to understand, and the vibe from the podcast was very laxed, which i appreciated a lot. I’m really glad i chose this subject too, because I have always had trouble understanding private, protected and public and the importance of it and it was just one of those subjects that has been overlooked a lot. So, listening to a full hour podcast about it and its functionalities and importance really helped me grasp the concepts. Overall, I am very pleased.

bottom of page