Object-Oriented Programming (OOP)
The first programming language I learned, mSL, uses a combination of event-driven and procedural programming. Each script I wrote was in a single source file, no matter how long. My largest script was over 1400 lines. The IRC connection portion was procedural and the channel protections were event-driven. Source files were loaded individually into the IRC client and interpreted. This was all normal to me as I had little-to-no exposure to other programming languages.
A few years down the road I discovered Java and, by extension, OOP. My first programs were styled similarly to my old mIRC scripts: one massive source file. I don't think I really understood what OOP was even though I was writing Java programs. I didn't really begin to understand until I attended community college. In any case, I have written a few useful programs outside of the classroom (mostly in Java). My latest project incorporates flow charts that I created when re-writing the project. It was a massive help. I have not created my own UML diagrams, but I was exposed to them in a previous class.
Keeping Up
Our lab assignment this week was a simple casino app. The point of the project was to test our ability to follow program specifications. We've been told this is not a creative design class and that we need to refrain from going off-script. I am often guilty of trying to reinvent the wheel. It's challenging for me to implement code that has been designed by others. I like doing things my own way. Hopefully some day I will be in a position to make the rules instead of follow them. Until that day, however, it is important to follow the blueprints that have been provided. I am looking forward to our first group assignment.
No comments:
Post a Comment