This is what you should do

-- "Auntie! Your wallet fell !"
-- "Thank you! Kids! You are really a noble person !"
-- "No thanks! This is what I should do. My name is young pioneers ......" (With a string of silver bell-like laughter, the children disappeared into the wind without a name ......)

Well, I admit that this is a spoof of a primary school essay of that age-the one before Han appeared. There is an implicit premise in this kind of composition: "It's not a waste of money, it's not a good thing, it's not a name." in that era, it will be judged as "this is what I should do ".

So after changing the background of the times, what is "what you should do?
In a specific profession (for example, the "Code farmer" occupation related to my blog), what is "what you should do?

Now let's assume that you are a coanon:

You are proficient in various algorithms and have slaughtered "pig" and "chicken" (beads and bread) for countless times. You just need to talk about the principles and applications of rbtree, bsptree, suffixtree, and hashtree; you will estimate and compare the O/M/Ω/OO of various algorithms. You know how to explain the algorithms in a simple way and how to program the implementation and test the performance, you can also select the correct Algorithm in your actual work ...... So do you think you are excellent, or do you say "this is what you should do "?

You are proficient in a lot of languages, and are also proficient in the "annoying" features of some "difficult" languages, for example, in C ++, the heavy-load resolution/partial template features/namespace/Multi-Inheritance/etc, you can also keep up with the "Latest Development" of the language ", familiar with GC/closure/multimethod/continuation/AMB, these "New Inventions" (well, well, these are not new, but just borrowed from lisp )...... So do you think you are excellent, or do you say "this is what you should do "?

You understand the development of most popular platforms and the APIs of most development kits. You can use various auxiliary tools for comprehensive and efficient debugging; you have a wealth of experience and a clear mind when solving the problem, as well as a careful experience in the case of positive evidence. You have a good understanding and Practice in Development, profiling, and testing, mode/refactoring/TDD/etc is a tool for you to work with, rather than limiting your cage ...... So do you think you are excellent, or do you say "this is what you should do "?

You know where the interests of different users are and how high the tolerance for software errors is. You know how users on different devices are used to operating. You know the functions that users are willing to pay, you know how to learn from and surpass competitor products, and you can keep up with the current user's expectations for functions (or even predict the future )...... So do you think you are excellent, or do you say "this is what you should do "?

You understand the significance of availability, can design a organized, non-messy interface, and can also use PS/AI/painter to make and program your design ...... So do you think you are excellent, or do you say "this is what you should do "? (Also, reference: is it a compliment to say that a software has "availability? Only qualified !)

You are proficient in computer principles, know the IO speed of various peripherals, have a refined understanding of their access methods, and write the device driver, in addition, you also know the magnitude of reliability of typical peripheral products ...... So do you think you are excellent, or do you say "this is what you should do "?

You have designed systems of different sizes, and you know what technologies should be used at what level. You know where performance hot spots are, and you are proficient in finding and Solving hot spots; you know how to balance functions, time, and quality, and how to choose between them under specific circumstances. You know the advantages and disadvantages of popular architectures, you know what kind of hardware can make up what kind of system and what kind of time is controlled on which level; you know how to arrange indicators to differentiate high-end and low-end products, you know what products can be provided under a given budget/cost, and you know how to perform cost down on the system without losing reliability ...... So do you think you are excellent, or do you say "this is what you should do "?

You are familiar with various software development models. You have accumulated a wealth of knowledge, but are not old-fashioned and have the courage to accept new things. You are very good at meetings, we can cancel the differences on the language surface in a short period of time to reach an agreement ...... So do you think you are excellent, or do you say "this is what you should do "?

You are hardworking and willing to work hard. You do not want to cheat yourself in your work. You have a big picture and pay attention to the details. You are gentle and helpful. Team members say that you are a very easy person to get along, even colleagues who have never met me are full of praise for you ...... So do you think you are excellent, or do you say "this is what you should do "?

......

You can ...... Yes ...... Also ...... Even if... You can also ...... So do you think you are excellent, or do you say "this is what you should do "?

......

If you have done the above, in my opinion, you have successfully completed your own job and completed yourself as an engineer (rather than a scientist) "What should you do"-Maybe you are much higher than the average level of people around you, maybe you exceed the average level of the entire industry, but does that mean "excellent? What if it's just what you should do?

Finally, as a celebrity, you can think independently and have a critical thinking on the basis of clear logic and rich knowledge. You know the economy and democracy; you are not angry, brainless, obscenity, or herd. You are not influenced by brainwashing and incitement ,...... So do you think you are excellent, or do you say "this is what you should do "?

Additional reading
(Each of the following links can correspond to a sentence in the above article for illustration, rather than proof)
Teach Yourself programming in ten years, by Peter norvig http://norvig.com/21-days.html
Why is it so fast, by pongba http://mindhacks.cn/2008/06/13/why-is-quicksort-so-quick/
Beating the averages, by Paul Graham http://www.paulgraham.com/avg.html
Http://www.xys.org/xys/ebooks/others/science/dajia10/zhongyi2621.txt