15 books for Java programmers: The Path to Java architects

Reprinted:

Iii. Path to Java architect

Wow ~ You have learnedJava architectNow you should be very skillful at using Java programming, and have a good programming idea and habit, however, you may still lack the ability to grasp the overall architecture of the application software. Now you are the first step towards the architect. Are you ready? OK. Let's go! Prepare a book for reading a typical entry-level Java architect.

1. Expert one-on-one J2EE design and development

This book is a famous book by Rod Johnson and is very classic.CodeSpringframework was born. But it seems that this book does not have a Chinese translation.

2. Expert one-on-one J2EE development without EJB

 
 

I don't want to mention it. This book is estimated that half of the world's students will take a look at it, but it is good to understand and understand 1% of the estimates.

This book was translated by gigix, with the participation of many industry experts. Although the signed translator is javaeye, javaeye does not contribute much, but it is truly the name of the translator.

The above two books are the classic masterpiece of rod Johnson, a must-read book for Java architects. Among the books I have recommended, I have read the most carefully and seriously. At that time, I almost read this book in an out-of-the-box manner, when I was a child, I picked up the lights and went to night to read Jin Yong's martial arts novels. The content in the book, as well as my own experience and knowledge, were thoroughly summed up. After reading this book, I was able to get through the channels, the feeling of explosive growth in power.

3. Enterprise Application Architecture Model

Martin has another famous book, but I have read this book extensively and have not read it carefully. This book seems more suitable for framework developers. For example, if you want to write an ORM on your own, this book must be viewed. However, it doesn't matter if you don't look at the application. But if you are free, I recommend you take a look at it carefully to see why the framework is designed like this, in this way, your level can be promoted to the perspective of the Framework designer to think about the problem. I have always admired Martin's books, but I have never read them as seriously as Rod Johnson's books.

4. Agile Software development principles, models and practices

The famous book of Uncle Bob, the classic masterpiece of agility, is quite special. It is not so much a book about the software development process as a book about the software architecture, this book takes a lot of space to talk about various object-oriented software development models. I personally think that after reading this book, you don't have to read gof's design pattern.

4. Software Development Process

Understanding the software development process is not simply an improvementProgramPersonal good programming habits are also the basis for enhancing team collaboration.

1. UML Essence

In fact, UML is not necessarily related to the software development process, but it is a tool required for the software team to collaborate and communicate and write software documents. However, there are not many practical diagrams in UML. It is enough to read this book and there is no need to chew on things like the UML user guide. I would like to remind you that the Chinese translation of this book is very bad. You are advised to read the original English version if necessary.

2. Resolve eXtreme Programming to embrace change XP

This is the second version of Kent Beck's masterpiece. There is nothing to say. You must read books.

3. unified software development process up

In fact, up and agile are not necessarily in conflict. Up also emphasizes iteration and testing, but the document and process-driven by up are not agile. In any case, up is worth reading. After all, there are very few enterprises that really accept agility in China. You still need to arm yourself with up, even if it is a pack of XP.

4. agile modeling AM

Scott Ambler's masterpiece, this book is very progmatic, telling you how to be agile and up, unify agility and up, and put forward many progmatic suggestions and practices. You can read three books, resolution eXtreme Programming Embracing Change, unified software development process, and agile modeling, to see the differences between XP and up, let's look at how am unifies XP and up, and combines these three theories into one furnace to form your own theoretical system. Then you can write a book.

Source: http://www.zhiweinet.com/