When a new employee asks, "What should I start studying from?", I try to answer "Let's qualify for basic information for the time being." The theory that no qualification is required is deep-rooted, but I personally think that the IPA qualification test is well done overall, and I think that there are many things that can be gained by studying seriously.
However, it is a fact that the work in front of us is not easy, or that it does not have immediate effect.
Fortunately, there are many Java books and there is no shortage of materials to learn, but I understand that too many books make me feel like "where to start ...". (I thought it would be nice to introduce a Java book now, but I feel that it is necessary now)
So, I would like to introduce a book that I have been reading Java and object-oriented books so far, and I feel that I should have read or should have read it in the first or second year of joining the company.
First of all, nothing starts unless you know the basic grammar. In my case, I chose Mr. Yuki's book, but in fact, at the introductory level, almost the same thing is written, so let's browse and find the one that suits you.
In terms of Amazon reviews, the "Clearly understand" series is popular.
UML
It's thin so you can read it easily.
UML will be used at work, and will appear in the books I'll introduce later. You can read UML without studying, but of course it is better to understand it correctly first.
『Head First Design Patterns』Eric Freeman, Elisabeth Robson, Bert Bates, Kathy Sierra / Oreilly & Associates Inc I read the original in English, but I have translated it. (I don't know about the quality of translation) I remember that the sentences were easy to read even in English.
I think it's the most straightforward introduction to design patterns.
There are 528 reviews on amazon.com and it's 4.5 stars, so it's a good deal. I forgot what it was, but I remember recommending this book, which is a famous Java book, with the GoF book as a recommended book for design patterns.
I read about Java, SQL, and networks in the "Head First" series, and they were all good.
"Design Patterns: Elements of Reusable Object-Oriented Software" (translated version is "Design Patterns for Reuse in Object Oriented". Commonly known as GoF book), which is the origin of design patterns (in software development), is squeezed in about 10 steps. Crushed to make it easier to read.
I don't think it's possible to suddenly read this "Introduction to Design Patterns Learned in the Java Language" and find that the content is too difficult to understand, but this book is just a catalog of design patterns, and "Why do you need design patterns?" The question remains, "What is it?", And I'm sure I'll get bored.
First of all, if you touch the design patterns lightly in "Head First Design Patterns", you will understand the necessity, so it should be easier to understand. I think that various use cases of design patterns have appeared in "Object-oriented mind", so even there.
Among the books introduced this time, the difficulty level may be a little high.
The content is the best, so I want to read it over and over again and learn it little by little.
A guidepost for writing code that is easy to read and maintainable. By trying not to write code that is subject to refactoring that appears in this book, you will naturally be able to write good code.
We also recommend "Readable Code" in the same genre.
SQL
It is rare to develop without using RDB (relational database) at all, so I want to know the basics of SQL This book has a very high degree of perfection as an introductory book, and basically this one is OK.
For those who want to deepen it, we recommend "SQL for Programmers" from "SQL Thorough Guidance Book Learned from Masters".
However, before you go that far, you should learn table design such as normalization.
Learn what you use in your business. If you ask a senior at the company, they will tell you something.
For Spring, "Introduction to Spring" is recommended.
Although there are few introductory books in this field, they explain carefully from the basics.
If you want to know more deeply, please go to "Java Concurrent Programming". (Translated version may be out of print)
I was confused because I introduced it in the end "I want you to read it in the first and second years", but the content is wonderful and I will list the book to read at the end
Recommended Posts