This year-I plan to write a Java book

With the support of many friends, I was determined to write a Java book this year. No matter whether I receive your attention, I will write every piece of content with my best efforts.

In fact, there are a lot of books in Java at present. In the opinion of experts, 8 or 9 of the 10 books are spam books, or they are not well written or really wanted, or copy it.

Maybe I write a book for two purposes. One is whether what I write can bring you value, or else I don't have to write it. Second, if there are similar books on the market, I would like to write a book that is boring. If I want to solve some groups of people and want to see a book that is difficult to grow up, please refer to the following introduction.

What is the main purpose of my book?

I (everyone can call me chubby or fat brother), and I dare not say whether I can really write really informative books, but there are still some accumulation in my work over the years, these factors are not only the technology itself, but also a kind of knowledge, ideas, methods, means and attitudes. In addition, I am helping many of my friends find that they are not technical, but the things described above. In fact, before they ask me, maybe I don't know the technology they use, even the technology they have never heard of, but I can solve the problems they have raised and quickly tell them why. In addition, the most confident part of my work is"Fast", There may often be situations where one person is doing things faster than a few people. Maybe you may think it is sloppy or a lot of things are not done in place, but maybe I am not doing this, and I may do better than others. I believe that this is not just the so-called "experience", but even less the "talent", because it was just like this when I graduated. I like to think about different things than others, in addition, I am not a very smart person. I can only say that I am not a too stupid person. I believe everyone can do it. So I wrote this book, we hope that people who are still confused can grow.

To put it simply, many people have crossed the river by feeling the stones on the shore of the night. However, some methods, mentality, and other factors make circles in the river. I hope this book will give you a rope, it is even a bridge, but it depends on your own courage and determination to cross the river.

What does the book contain?

Maybe in this book, knowledge is a guide. How to deepen, accumulate, and improve yourself becomes the key and advocate "learning from the Sea". No one can understand everything, therefore, you should learn more about the ability to quickly learn, quickly grasp the essence of the ability, and quickly enter a certain field of ability.

I am not writing a full list of codes, and I cannot write it fully. Society is constantly improving and developing. It has been a pattern for several years. Maybe you will work across industries, work across technical and business fields, and so on. You may face a lot of problems you haven't faced in your life, especially in this age of rapid technological changes, I believe that these things are a valuable asset, not just how to use a technology.

I will not give a very comprehensive introduction to the content of some sections, because the introduction is incomplete and meaningless, because there may be new versions and features tomorrow, however, their main channels and thoughts will not change significantly.

The first article in the book will introduce the basics in six chapters to illustrate the knowledge that a Java programmer should possess. I also believe that everyone is admired by many programmers abroad, and we should not be much worse than others. Should a good Java programmer only write some common Java Business Code all day long? Can you solve the problem? Maybe you will understand something after reading this article.

Next, I will read the source code in Chapter 5 of Article 2, which will be explained using the source code that many Java programmers will use.Never"The source code I wrote is too tangled, because you may not be able to use the source code at all, the purpose of my source code writing is to let many people who are entangled in how to view the source code (some people look at the source code, but some people can't remember the source code) and learn how to look at the source code, let's look at what technical reserves should be available before the source code, what should you learn from the source code, what is the purpose and original intention of the source code, what is the author's idea, and why should we design it like this, what should I do when I work as an architect? I hope that you will eventually achieve this even if I have never played this thing, but it does not mean that I cannot finish it. Maybe I can play it more smoothly than many people who have been playing it for a long time in ten minutes.

In chapter 3 of Article 3, we will introduce the designers. Because a good Java programmer will embark on this path sooner or later, and this path is not something that you will become a designer tomorrow, it was a process that should be developed at least in terms of consciousness at the beginning, so I wrote this content and I will use some examples to design it with everyone. Maybe these designs are not the best, but I hope that you can learn the design methods and ideas, instead of getting stuck with examples and learning to bypass the analogy. I will also bring out some "design patterns" from the instance usage, but they may not be complete, so that you do not need to worry about the design patterns themselves. In many cases, when you do not have that experience, it is often counterproductive to stick to your back or stick to it. I will tell you how to use the design pattern here. It does not exist for"Cool", But the value and meaning of its existence. In addition, it is like the tactics in martial arts are dead, and talents are active.

In chapter 4, we will use Chapter 2 to describe the instance model and Chapter 2, because I didn't want to write this part, but since Java is mentioned, we will still mention some implementation-level things. We will use some cases from the design process to the implementation process, how we think about it, how to consider the user experience, and how to face the brutal demand changes, how to deal with technical innovation and repetitive manufacturing, how to deal with some collaboration issues, how to do some tests, and so on.

In the last article, there will be six chapters, which are extensions and arguments. Apart from the knowledge that some programmers should know: Ui, cluster, and distributed, we also summarize some "pitfalls". Through pitfalls, you may learn more about things that need to recognize the essence, and even the surface is not necessarily the most authentic. At the same time, we used to see how to quantify and weigh the use of some technologies and whether to use them. We didn't talk about it with numbers. Finally, a programmer should find his own foothold, recognize or find the real value in his ordinary work, find his own technology and business direction, and explore and innovate in depth.

What is the style of my book?

I used to be a person who didn't even know what a computer was. What I wrote was not necessarily completely accurate. I just wanted it to help you, I want to read books that interest me, not books that I want to go to bed. Even people who are not doing it can read some books. I will try my best to write them like this, I hope you can enjoy reading and growing up happily. However, this kind of expression lacks rigor and may mislead readers, I will try to explain something as much as possible: I mean this, not that.

In addition, out of respect for knowledge and depth of technology itself, some content will also be more serious.

Finally, although I will write the source code and examples, most of the sections in the book are"Do not rely on code pasting"To complete, most of the content is done by hand, may use some examples on the network, but generally after some improvements, modifications and finishing, try to present it in a clear way.

Why is it so complicated?

As mentioned above, this is actually some of the qualities that I think a Java programmer should possess, because I am not writing the technology itself, instead, we discuss various ideas, methods, and attitudes that we usually use through knowledge, design, examples, and source code, in addition, in terms of technology, the extension of one person is also an important support. In many cases, it is related knowledge that gives you a deeper understanding of your major. As for the direction and field you want to go deep, it is your choice. In the last chapter, I hope you can find your own direction gradually.

Suitable audience?

Many of the contents in this book are simple and simple, with stories. The first type of suitable audience is those who want to quickly find something to understand, second, there are some people with weird ways of thinking and complicated simple problems. I hope you can relax and understand the truth of technology. Even if you are not an IT specialist, Maybe you work with IT technicians. You may have looked up and looked up. Maybe you can talk to him one day.

Another type is people who are confused during growth. Maybe you feel that your work is meaningless, maybe you do not know where to learn or develop, or you may feel that you are doing too many tasks to find a position, this book may give you some suggestions.

Unsuitable audience?

If you are a cool man, this book is really not suitable for you, because it cannot help you change from a cool man to a master;

If you are a client, this book is suitable for you, because a lot of content is based on servers.

At last, if you support me to write a book, I will do my best to write the book. Because of the manual writing and busy work, the writing speed will be a little slower, now I have written more than two chapters of the first draft. This book may be available to you in about 4-6 months.