Reading diary mo Yu "A Programmer's struggle history" Java Interview comprehension programmer __java

1 Experience 1.1 for employment, Shenzhen is a very realistic place, he will not ask whether you are a key university graduate, not to ask you are SM degree, more value is personal experience, you can do things. 1.2 A programmer, must often learn, not lag behind the times, to actively learn new technology 1.3 Hong Kong and Taiwan enterprises pay attention to the young and the elderly, subordinates can not directly call the boss's name, and in order to close and embarrassed, so from English, such as Mike; 1.4 for programmers, learning from the basics is best, and when it comes to the company, it's not that important what a person can learn, but the most important thing is when you can get the job done . 1.5 A lot of beginners began to look at the technical books attitude is not correct, pick up a book, turn a few, found that do not understand, all over, the mind to wait for later to see understand again. This is a pseudo proposition, heat should be good reading, superficial understanding for a beginner, the beginning of a thing is never touched, is absolutely vacant, can not even use search engines do not know what the keyword, and if the previous read related books, you can press the impression to search. (Zzz this matter of opinions) 1.6 When working, remember to back up your code 1.7 When job-hopping, can not directly reuse before the program, copyright issues, but should be extracted from the core code block, and then refactor the logic layer code, programmers job-hopping-with class run, In other words, layering the code according to its purpose will benefit both the company and the individual 1.8 A lot of fresh graduates, when the top of his favor, often easy to be complacent, beginning many colleagues are not pleasing to the eye. So slowly, a lot of colleagues do not like him, slowly he was isolated, and even may be colleagues in the back stab knife, finally fell into a mess ... 1.9 insist to write a blog, and technical articles are very deep, perhaps Mo Day, be recognized, step back can also write their own to see it 1.10 The second is to know what algorithm concepts, know how the corresponding algorithm library how to use 1.11 Read more books, is very important to programmers, may not see when the Greek, when as long as you have a little impression, know that there is one thing, perhaps such an inspiration, will save a lot of trouble for the future work 1.12 In small companies, to raise the call to the leadership, in the project can not be separated from you when raising a raise. 1.13 Interview, do not understand the question can not understand, not a meal nonsense 1.14 Smart Employees in the beginning of work, there is no chance to find the opportunity to copy a copy of the message to the leader, one is the exemption, and let the leadership know that they are really doing things 1.15 can become Daniel, to have the initiative, they will take the initiative to learn or try new things, 80% of the time to complete the task of leadership, 20% of the time to explore new knowledge. 1.16 Books to see more than a hand to do, the code to do their own line of play 1.17 To learn in front of leadership performance, and more contact with the leadership, only need to chat, elevators. 1.18 Use blogs to share technology, 1.19 Veteran is even if the answer is in front of the hand to verify 1.20 sometimes hear some top secret, do not everywhere nonsense, this is not only the company confidential, may or on the machine set the trap 1.21 for programmers, there is a maxim: The general code of the problem is not a problem, as long as others use the code can make things, you will be able to do it.
after reading this book, the intention is still not exhausted, very want to see the author's second book, very humorous, 360 praise ...