A little organization never hurt anybody

Plus a piece on object-oriented programming.

This is the fourth week of class and I have decided to start keeping a ‘journal’ of sorts. It’s more like a fancy notebook for the course. I guess I jot down certain key words, definitions and diagrams. We have just started linked lists in this course and that in itself is avery diagram-driven concept.

The diagrams only get messier from here I’d say.

One another note, however, one of the suggested topics to write about this week was object-oriented programming. Albeit I have no idea what that meant before today, I’m going to list a few definitions and the pros and cons of ‘OOP’ in this Slog.

Object-oriented programming is a model structured around objects and things rather than ‘actions’. Programmers who adopt object-oriented programming languages tend to self care about the ‘logic’ required to make a task happen, but rather focus on an object being manipulated to accomplish the task. (At least that’s what my current understanding of it is. I’m sure this paragraph will change towards the end of this course)

Python programming uses classes.

Python has been an object-oriented programming language since its inception due to the fact that a user can introduce classes to design the software structure however they’d like. This makes the programming environment much cleaner and as a result actually working on the problem at hand far more efficient.

Through ‘inheritance’, data is easily accessible through first defining classes and then subclasses. This cuts development time down and ensures more accurate coding.

Bottom line is: Python is cool as $#!T so far. I’m looking forward to the assignments in this course.