#opaat

Note: Due to being basically a two & half old decade book, the infomation inside will unboubtably be majorly out-of-date. However my hope is by improving even just my theortical understanding of some form of coding, even coding that may not be in use anymore, I will have a easier time understanding the coding of today.

Note 2: I'm typing this all out by hand, without a word-checker, while having dyslexica. There is going to be both spelling mistakes, and missing words, it is going to happen, it's probably already happened. So in the kindest way possible, shush.

PAGE 1 (A.K.A Page xiii) "We have made a number of improvements in this second edition of the book, but the main objectives remain the same. This book is intended as an introductory text on object-oriented programming, suitble for use in a one-semester CS1 course, and assumes no prior programming experience from the students. Those who already have experience in traditional process-oriented programing languages such as, C, BASIC, and others also can use this book as an introduction to object-oriented programming, graphical user interface, and event driven programming. The two main objectives of this book are to teach

Object-oriented programming.

The foundations of real-world programming.

Object-orientation has become an important paradigm on all fields of computer science, and it is important to teach object-oriented programming from the first programming course. Teaching object-oriented programming is more than teaching the syntax and semantics of an object-oriented programming language. Mastering object-oriented programming means becoming conersant with the object-oriented concepts and being able to apply them effectively and systematically in developing programs. The book teaches object-oriented programming, and students will learn how to develop true object-oriented programs. The second objective of this book is to prepare students for real-world programming. Knowing object-oriented conecpts is not enough. Students must be"

The following interptation will by subject the the authors own personal bias infulincing the text, and my own biases, as well as other factors. This will be true of all other following interpitaions of any part of this book by me. It should be understood therefore there is a high chance of innacuries, and none of this should be read under the false notion of it being factual.

My Interepitaion:

— This book was aimed at students

— It is an option for complete begginers

— It is an option for those with programming knowleged (fuck i can't spell)

— It is an option for those who program in programming lanaguages that are not Java (C & BASIC used as an examples)

— There is a difference between "process-oriented" and "object-oriented" programming. My utter shot in the dark theory, is that maybe the difference is that object-oreinted means it's so do with assests (e.g A cube in 3D space, or a "Button" on a website), and process-oriented is less about reacting to what happens if the ball goes through the hoop and instead about telling the ball it's going to go through and with what calulations the ensure that happens 100% of the time. Process-oriented is sum not a response to a bunch of subelty chaning varibles????? Idk, I just don't understand programming enough to know if there would ever be a difference to what actaully is going on in the code in what way, in the end it seems programming is a bunch of instructions, isn't it always only ever going to do exactly what you tell it to and never ever anything you don't? EUGH, I'm yapping too much

— The book may also touch upon "grahical user inerface" my theory is this is to do with UI like you might find on a website page, or a menu of a game/dvd, etc

— The book may also touch upon "event driven programming" I would theorise this is do with a user interaction triggering programming to occur, for example a user typing into a search bar & pressing enter and the program loading up various assests in response. However, I don't see how could be unqiue? Isn't that all programming, IF, ELSE, and all that? Why would it even have a name or be metioned if that's all it was? So in short, idk yet

— To me it seems like the author might be implying that Object-oriented programming if understood properly should impact the way in which problem solving and desgin is apporached overall, beyond just being able to learn the "syntax", aka what you need to type into the progamming software, how you use Java to do this form of programming

— The author belives that Object-oriented programming should be taught from the very start of someone learning programming

— The author belives that in order to master Object-oriented programming you need to be able to use it while programming both "effectively" and "systemtaically", aka. in a way that actually works, neatly, and when it's actually applicable/needed (Also DON'T take a shot for every time you read "Object-orient programming" you WILL die. Lol)

— There is a concept called "real-world programming" my theory is this is the difference between a program for software is purely online, and software for hardware like traffic lights on a "real-world" road. Although it's all ultimatly digital when it's programming so that interpitaion seems symatic, an online bank is still pleantly "real-world" in terms of impact in it and it's not just the safes & cash machies that have to be impacted to cause "real-world" problems. So I'll assume I'm just inncorrect about that interpation of the author's words for now