Foreword
Before we talk about the programmer's "35-year-old crisis", but now the programmer's getting lower and lower threshold, for most programmers, the 30-year-old is already in crisis .
Many programmers define the mix of good, that is, the 30-year-old forward did not have to BAT, but millions of domestic programmers few of the BAT. Technology is one thing, more often into the BAT also need some luck . Can go is great, but also no need to get into that life without hope. Many small and medium companies programmers had not worse than BAT. Of course, BAT is a lot of programmers into obsession, this is another matter
I share alone, can not let you directly into BAT, but if you carefully read this article, at least you can let programmers in this road go farther, I lived not too bad.
01
First of all, you have to recognize their own , this is the time to plan their career path, we must first clear thing.
Programmer's career is about to start from the age of 20. 20-year-old we are doing? Maybe sway youth in the ivory tower of the campus, maybe we are out of the school into the workplace
If your school is not very good, it is the practice (project) in the first place, while lowering your expectations or you will be very anxious, anxiety is not a good thing.
"Without a good education would take the works speak for themselves."
Work is the best proof of a programmer, is a lot more than you want to resume those bells and whistles. Many programmers say that this is self-deception is not a good project, whether it is involved in open source projects or their own as much as possible to imitate this is a good practice good Internet project.
This also applies to a BAT students want a new job to go to work now is not very good. Be able to put on the table with the strength to make up for the lack of education is the best way to manufacturers. If you have a project in 2000+ Star is actually very easy to manufacturers.
02
About learning languages, I recommend three languages!
It is strongly recommended that you learn Java, which is very good for training programming thinking, since Java is representative of classic programming thinking, and many of the classic dynamic programming language is not thinking stressed or very easy to overlook.
Many back-end can easily become a full-stack developer precisely because they are from Java programming beginning of the road, starting from Java to learn another language would be more relaxed, but in turn start to think of learning from Java dynamic languages, Go other languages is not so easy.
In fact, Java, C #, C ++ can be any one of the three, we must choose this type of classic programming language, taking into account the practicality, is still the most appropriate Java, Python, and JS are not the best choice for the language, but as a second language They are the most appropriate.
This is the thinking in Java:
Software engineering thinking, whether or JS Python actually have such a demand, not because you do not need a dynamic language, many students do not understand the source of too much food or not their syntax is familiar, but the "software engineering thinking 35 "no, do not understand why the good have to write framework code is very complicated.
Multi-lingual is a good thing, but:
Language is not the pursuit of multi-purpose, capable of flexible application in multiple languages, it is the real power.
Many students at the front end looks very magical thinking and mechanisms in fact, in the back-end programming is very common, such as the concept of design patterns, IOC containers.
Many people say that the algorithm is good programmers and programmers of ordinary watershed, this sentence is correct in the past. But for now this software package height thing:
Ideas and design pattern is the real watershed
Meanwhile, many students often ask me: Teacher, I am confused I do not know how to learn, I do not know in the end to learn to what extent. The problem, in my opinion, it is essentially because we are putting the cart before the technology. Technology is a very practical thing, do the technical examination-oriented education are not the kind of learning mode.
Technology to service revenue, to be applied in practice!
Some students say, I just do not know how the technology is applied in practice. It's very simple, you can participate in an open source project or give yourself a virtual project.
03
Why do we say that 30-year-old programmer crisis?
If you think about the age of 30 simply relying on technology to eat, basically not realistic. Cheaper than you young people, you can not pay the required 30-year-old and 20-year-old man. What do you think you and the 20-year-old man than to your advantage? experience? Sorry, the experience was not that big a gap for programmers in this industry. because:
Software has been modeled, and it is not a sophisticated industry, your experience may be worthless
So 30-year-old to fight the overall quality, capabilities include communication skills, leadership, management skills, analytical problem, your experience was worth only a combination of these capabilities, technology accumulation before you combine these capabilities can only continue to shine.
A lot of people do technology, and my heart to do is look down on people management, I used to think that technology is a pure, management can be doing, but with grow older, I understand the truth: want to have higher returns, We need to provide greater value to business and society. The value of a person is limited only technology, but different management, so that management can maximize the value of a group of people , which is why the management of payroll, certainly a lot of reasons to be higher than that of ordinary skill.
That how to develop these capabilities? These seemingly very true but very important capability, in fact, did not like the technology as a learning path. Many students say that I am 20 years old, still young, I should first learn technique, so I learn a technique to consider these issues. Wrong!
Have you ever wondered why the same two people in the same company, a person's salary can be 1 times higher than another or even several times, why pay someone else every time the magnitude taller than you? I took a lot of teams, I know very well why the technology is definitely not the main point of difference. To have a basket, and we monasteries, who more than anyone else's technology in daily life can be much worse? In fact, the main difference is the comprehensive quality: can handle all kinds of things in perfect order, but also to their principles, the thing to do is simply beautiful.
To give an example to me, this document is a man of my team do. I actually complete such a document only said three words: 1. there is a sql join the document. 2. style good point. 3. Logic distinct dots.
From two angles to think,
First, you are a leader you like that employees do
Second, if you do you can do it at this level
If you have the capability not worry about the future, and this is reflected in the overall quality. In fact, the overall quality of all walks of life are demanding, but often little alternative programmer this career, most people do not value the overall quality of just blindly fierce techniques.
You can carefully observe the many highly paid people, they all have a common characteristic, that can do well.
其实技术这个事儿越到后面越不值钱是很正常的。其他很多职业是先付出才有收益，但技术不同，它只需要付出少量的精力突击学习就能找到一份还可以工作，这和其他需要前期投入很多成本的职业不同。这个行业门槛偏低享受了低门槛的优势就必定要在未来付出相应的代价。
那我们究竟该如何面对未来呢？
程序员在未来大抵有以下4个方向
1.技术一条路走到黑
2.半技术、半管理的复合人才
3.自主创业
4.直接转行
后面我会带这大家一条条分析。
第一条能在技术上一条路走到黑的少之又少。能走这条路的很大程度上是真需要一定的天赋的，大多数人走不到黑就爬不动了。
第二条是去兼具技术和管理
第三条这个不多说了，能自主创业成功的那是你的能力。如果你有这个能力我觉得基本不需要听其他人的意见，你必定有很强的自我选择和分析能力。
第四条也有很多人走但大多数是被迫无奈只能转行。
最实际的，也被大多数前辈证明确实可行的，只有第二条。有很多同学说做纯管理不是不可以，只是没有优势！你20岁－30岁都在为技术奋斗，这些积累需要物尽其用的利用起来，技术是你傍身的优势不能丢掉。只有兼具技术和管理才是你最大的优势。
这就是为什么前面我特别强调技术不是唯一，把事做好才是你的目标。我们很多同学体会不到是因为你从来都只站在一个执行者的角度去看待问题和完成任务，从来没有站在一个leader的角度去看待问题。你必须和你的leader保持同理心。时间长了你自然就具备了一定的管理和分析能力。
把事情做好的一个先决条件是你有一定的大局观和分析能力，这一点非常重要！这也是为什么很多人到了30岁后无法转技术管理的原因。你20多岁的时候只知道每天耕耘自己的一亩三分田，做前端的永远不学服务端，做服务端的永远不了解前端你，如何能有全局的分析能力和大局观？
前端这个称号其实是人家给你画的圈，不应该成为你自己的枷锁。其实在我心里从来就没有全栈，在过去本身就没有前后端之分，何来全栈之说？很多同学说过去不分前后端是因为没有那么多的框架要学习，这是本末倒置！还是抱着考试的态度在学习。
在我看来现在的前端比过去简单太多了，开发一个项目的成本比过去低太多了。jQuery时代是没有组件化也没有数据绑定的，想想只这两点能节约多少成本，以前你需要自己用原生的JS模拟类这个概念，因为那时候没有ES6，想想现在的ES标准。
不要给自己贴上前后端的标签 因为你扼杀了你自己的可能性
事实上现在技术的发展趋势也是模糊了前后端的界限这个就不用我再多说了。
走第二条路还有一点非常重要——注重细节。一个产品的细节才是灵魂，好的程序员和不好的程序员其实在技术本身上差异不大，但是好的程序员非常注重细节。如果你写代码的时候努力去做好细节，那么长期积累下来学习的效果是非常明显的，进步也会非常的快。如果你总是觉得差不多就行了，写出来的代码千疮百孔，那我建议趁早放弃编程。
最后强调一点，学习太多方法论不是一件好事，以解决问题为目标才是最好的方法论，没有之一。我们很多同学特别热爱去看方法论，方法论本身没错但问题是我们没有坚持下去的毅力，也没有这个执行力。方法论的前提是你能很好的执行它。所以我们需要有驱动，解决问题就是最好的驱动力。太多同学迷失在方法论的探索里，永远在找方法就是永远的停滞不前。
说了这么多，肯定有人在心里问，道理我知道了，怎么落地，怎么实操呢？
捷径就是向比你厉害的人学习，在实战项目中学习，突破“端”的界限去学！
最后
文章的经验分享虽然到这里就结束了，不过小编为大家准备了Java相关的实战文档作为文末的福利，希望可以给程序员朋友们提供到可以有所提升的帮助！均免费分享，大可不用担心。
获取方式：转发+关注后后台私信【实战文档】可免费领取！
