Original link:
https://bss.csdn.net/m/topic/dev_survey2019?source_id=zx
Author | flat head brother of technical Bowen
Zebian | Tu Min
Produced | CSDN blog
Pay attention to the principle of knowledge
Under the current Internet environment, focusing on the principle of knowledge and learning programmers less and less, especially in this environment explosion training institutions, online you will often see something like three months from the entry to the master high concurrency, distributed advertising, training institutions and I believe this technology has the ability, but I do not believe there is a beginner such a good reception. Even an instructor training institutions, there is a 1997-born architect, early 20s became the architect, it really is Houshengkewei. In my mind, the architects are not out of school, through the project architect is fed out. Well, we get down to business.
Why should we pay attention to the principle of type knowledge? Because knowledge is the principle of our roots, I cited three examples of this view will be explained.
1, design patterns you know, whether you are doing system architecture design or read the source code open source project, you will find that they are not open around the final design mode.
2, you know data structures and algorithms, high concurrency in this against the clock, time is money at the scene, you know List, Map of how the trade-offs.
3, you understand the principle of network communication, system architecture when we do, the problem will be of great help to exclude.
It can be said that the principle of knowledge determines the lower limit of the programmer, strong knowledge of the principles of the programmer, the lower limit is not too low, on the contrary, the principle of knowledge is not strong programmer, I believe the cap will not go high.
Build their own core technology stack
Code code farmers farming circles have always been middle-aged sense of crisis, even those farmers have not yet entry code, programmers only do they know that to 35 years old. I do not discuss this point of view is not, to put it all the time, you get to 35 years old that year, this topic will naturally have an answer. Most programmers have a midlife crisis awareness, so when just getting started, it will take more time to learn. Many people will go wrong in this place, it seems to spend a lot of time to learn, but with no progress even in the relatively backward, why?
很多程序员包括我在内是这样学习的，现在大数据这么火，买本书、看个视频学习一下。学了半个月一个月后，大数据太难了，学不动了，先放一下。咦，这个推荐系统好像很有意思哎，又买本书学习一下。最后就在一个循环中，每一项技术都在学，每一项都是一个入门。看上去啥都会，真实做的时候，发现啥都不会，就是这么的神奇。
这就是一个怪圈，很多程序员都会跳入的怪圈。对程序员这种技术型的工作来说，这是学习的大忌，因为技术行业知识广相对知识深来说没有优势，在公司专人做专事，需要的是技术深度。所以我们每个程序员需要打造自己的核心技术栈，你搞 Java Web 开发，那么你在某一个方向上，比如在高并发、消息中间件或者分布式架构比公司或者周围的程序员有更深入的学习研究，这会成为你升职加薪或者跳槽的资本。
做自我驱动型员工
在职场上有两种员工，一种是任务型员工，一种是自我驱动型员工。任务型员工，领导安排什么活，干完就了事，从来不会想着，我写的这个功能有没有优化的空间？为了任务而任务。这种员工只能待在这个舒适区，哪天舒适区不要他了，估计很难找到安身之处。
自我驱动型员工恰恰相反，他对每出现的问题都会反问自己，这个问题出现的根本原因在哪里？为什么会出现这个原因？我该如何避免再次出现这类问题？对于每一个问题他都会找出最根本的原因并且提供最好的解决办法。
对于公司使用的每一项技术，他都会去了解技术背后的原理，这种技术的应用场景在哪里？优缺点又是那些等等，对于自我驱动型员工来说，根源才是他的最终答案。
自我驱动型员工更多的会带着自己的思考去做业务，对技术刨根问底，追求原理的过程，会是一个快乐的过程，思考多了就会找到场景与原理的关联关系。自我驱动型员工的成长比较迅速，在短时间内会拥有自己的核心竞争力。
记笔记，写博客
记笔记，写博客是总结与分享的行为，这不仅是程序员，这是所有人都应该去做的一件事情。记笔记是对你过去的总结，把你学到的重要的知识记录下来，方便你后面的查阅与重温，老话说得好：好记性不如烂笔头，记下来总是没错的。
Write blog is a shared process, put your knowledge to share out the form of text, it might help a lot of people, this process was happy. Write your blog is a good way to check knowledge of Network access, write a blog on the road, will continue to refresh your understanding.
Disclaimer: This article is the original article CSDN blogger "flat head technology Bowen brother" of.
Scanning the next Fanger Wei code, see bloggers wonderful to share!
Thermal paper recommended
☞
☞
☞
☞
☞
Click to read the original, wonderful to continue!
Your point of each "look", I seriously as a favorite