I thought it would be nice to read the "Object-Oriented Practical Guide", so I made a note for myself. It's still on the way. I read it about a year ago and thought it was a good book, but when I read it again, I have a lot to learn.
No application has changed. Change will come in any application. Applications that are easy to change are fun to write. On the contrary, it costs money and becomes unmanageable. Parts are "objects" and interactions are "messages" passed between objects. => This is important.
Design is the composition of the code. In other words, the application itself.
Object-oriented design tools
** Design Principles ** SOLID principle => It's a famous guy. I am conscious when writing code, but it is difficult to embody.
** Design pattern ** GoF, design pattern
It's a convenient tool, but it is possible for beginners to misunderstand the intention and design it in a way that does not match the original intention.
The reason why the design fails is that the design is not enough. Ruby is easy and anyone can write it. However, on the other hand, undesigned applications are prone to failure.
Also, programmers who know how to do object-oriented design but don't know how to apply it run into another mistake.
After all, I feel that what is called a good book has a lot of learning.
--Readable code --Refactoring Ruby --The way of a master programmer --SQL Anti-Patterns
etc. If I have time, I would like to summarize these books as well.
Recommended Posts