Top engineers talk about opportunities, talk about job-hopping and choice

Today in the watercress saw an ebook, this book is not thick, but also 100 pages, but the title is quite bluffing: the annual salary of 200,000 to 800,000 attack, subtitle for high-end programmers how to jump-job. Generally I see this title of the book, whether it is an ebook or a paper book, I choose to ignore it. In my not too much reading "career" (in the range of memory, not counting school textbooks, counseling books, etc., I read not more than 200 books), my methodology is the book is not how much to read, but to read a good book, read after the understanding of how much, After understanding what is the improvement of your own material level or spiritual level, and even what kind of positive energy can be conveyed to others after comprehension. To tell the truth, I was entrap in the process of choosing a book, so far I have felt anger. So, I can imagine, when I face the above such a book, My attitude is how, and that book is still charged. But I chose to buy the book, Why? One of its comments touched me: All the income will be donated to Wikipedia. I am a person with an idealistic complex in the heart, has always been the cause of Wikipedia is extremely respected, so directed at my inner idealism, I bought this book. It was a bit far, we went on to say the book. This book is divided into three chapters, of which the first and second chapters are mainly combined with some specific offer auction data to select the analysis and give some suggestions, the third chapter is the access to two top programmers, I read after, Lenovo to my current situation, feel good, very helpful and inspiring, So the inside I think a good fragment to share with you, one is to change their past has been very bad reading habits: After reading no records, no thinking, and the other is to exercise their own writing articles, speak clearly one thing ability. Well, there's not much to gossip about. To share the content below, some of the sections add some of my personal reading comprehension.

1. Talk about communication: Speaking in public is a very useful skill

Many times you are too familiar with many things and assume that others are as familiar as you are. But the reality is not so, you need to continue to communicate effectively, others can really understand.

2, talk about opportunities: there is no underappreciated in the world, is to understand each other

Me: Who says no, many team-work failures are often poorly communicated or communicated, but without mutual understanding.

3, talk about the workplace: The boss needs is not the most hard work, but the most able to communicate with the boss

As a programmer, even if you can write code for 24 hours, it's not that big a contribution to the company. For the company, the most important thing is to go in the right direction, and this direction of choice, in fact, depends on the boss and the board. In the workplace, the relationship with the direct boss can be said to be the most important. As programmers must not be preoccupied with coding, to understand the entire company's architecture, business model and direction, to know that many times, the boss most need is not the most hard work, but the most able to communicate with the boss. As an employee, try to think about what you are doing in the perspective of your boss's position. This will be more able to grasp the focus of the work. The so-called leadership, the most important thing is: think clearly, communicate clearly.

4, talk about mastering communication skills: Learning Wikipedia's writing paradigm

It's a great writing paradigm to see Wikipedia more. Learn about Wikipedia without emotion, position, presupposition to tell one thing, concise and clear way of expression.

5, talk about the daily: Independent thinking is a very important thing

So-called independent thinking, you can use this methodology to think about the question: Where does this information come from, media indoctrination, or self-thinking? Toyota's 5 Whys analysis method is very good. The method of quality control in Japanese enterprises is a kind of analytical method to find the root cause of the problem, which has the rule, order and no omission. As a software engineer, it is especially necessary to have the awareness and ability to analyze problems in the work. At the same time, when describing a problem, it should be in the most accurate manner possible. For example, as a front-end development engineer, do not say: The site is open slowly, but can be used in a similar way: DNS resolution spent 300ms, the establishment of a connection spent 100ms, and then spent close to 600ms waiting, the backend needs to be optimized.

Written in the last: maybe a lot of people read the above content, think is a chicken soup, in fact, I want to say whether it is not chicken soup, as long as it prompted you to make a change of even a hint of the idea of silk, I feel is good.

*_*, what I say is wrong, and of course includes this sentence.

Top engineers talk about opportunities, talk about job-hopping and choice