A memorandum that summarizes what I learned in my second month as a development engineer. Recently, I've learned a lot of new things every day, and I can't keep up with my feelings of fun and a lot of information! !! !! It is supposed to be. I will write it like my own external HDD!
↓ By the way, click here for previous articles -15th -16th -17th
I posted two articles today (. ・ V ・) ノ
--Object ・ ・ ・ Object, object, purpose (from weblio English-Japanese dictionary)
--The way of thinking in development. --A development method that considers the application to be created as **.
--The basic idea is [above](https://qiita.com/icchy_sh33p/items/dc00f27d8cb6cc2f4385#%E3%82%AA%E3%83%96%E3%82%B8%E3%82%A7%E3% Same as 82% AF% E3% 83% 88% E6% 8C% 87% E5% 90% 91% E3% 81% A8% E3% 81% AF). --Created by instantiating based on the class and the code written in it → In other words, the image of ** making things from blueprints **. --There are two, ** class ** and ** instance **.
--Has a role as ** "blueprint" ** in Java. --Since the actual design is done in the class, the following things exist in the class. -** Method ** ・ ・ ・ Created in the blueprint ** Describes "behavior" ** -** Constructor ** ・ ・ ・ Processing created at the same time when creating an object
--The real thing. Recognition that it is actually made. --Class ** instantiation ** ... A class that has been made real and can be used in that class. The result of instantiation is ** object ** = Class is ** Object blueprint! ** **
--The basic idea is [above](https://qiita.com/icchy_sh33p/items/dc00f27d8cb6cc2f4385#%E3%82%AA%E3%83%96%E3%82%B8%E3%82%A7%E3% Same as 82% AF% E3% 83% 88% E6% 8C% 87% E5% 90% 91% E3% 81% A8% E3% 81% AF). --In the case of JavaScript, one of the major features is that ** classes do not exist ** --There is a ** prototype object ** instead of a class -** Prototype object ** ・ ・ ・ Object as a blueprint (created so that you do not have to write the object every time) --** Objects in JavaScript ** ... entity, real thing (** close to an instance in Java **). ――It is difficult to create the same object many times / I want to add a function
→ ** Prototype object ** was created to make it easier to handle using the original object. → In other words, the image is that ** we will seek easier creation using blueprints from the original ones **.
--Same about the underlying object-oriented thinking in both Java and JavaScript ――By seeing the object to be developed as ** "things" **, the blueprint and the substance exist. ――However, the approach is opposite in object orientation. --Java has the image of ** assembling and completing things based on the blueprint ** ――The image of JavaScript is that ** further blueprints and entities are created based on the created entity, and the final product is completed ** using them.
I was talking about the importance of object-oriented programming since I was touching Python, and while I was learning Java and JavaScript, I was a little careful, but how much do I understand? I wondered if I knew it properly in the first place, and I thought it would be okay to put it together once, so this time I decided on object-oriented programming!
To be honest, I didn't really understand the image of the object, and sometimes I knew this thing but didn't understand what it meant ... but when I put it together, I researched it again and read a reference book. I think I managed to reach a level that I can understand now.
It may take some time to output, but since I can organize and supplement the information in my head, I realized again that it is important to be conscious of people in this way. !! !! !!
I will summarize it again! !! See you soon
Recommended Posts