Everyone, will inevitably shake the gains and losses in the process of growing up, for me, the future how best to balance the pros and cons, is the need to think about, but for young new entrants, the summary from me these get a little inspiration, I would quite pleased. This is also where I grew in significance of the art summary of gains and losses.
1. growth posture
As a technical person, we must first consider is the technical growth, while on the subject, there are three general statement that depth-first, breadth-first, or a combination .
Depth-first
That is, vertical development, coming mostly focus on a technical direction, and then become an expert in this direction. For example, some people after graduation has been doing desktop software development, so that after ten years to become experts in the desktop software development, some people have been using Java-based technology development, after a long time can become an expert on Java development direction. These people have a very rich experience in a single direction, we can quickly resolve various technical issues in those directions, or give technical solutions. For now, more popular manufacturers such technical personnel, they can work independently in their own direction.
Breadth-First
Also known as horizontal development, in general, is in contact with a variety of technologies, using various frameworks, both involved in front-end development, back-end and participate in the development, operation and maintenance, or even participate in the test. Such techniques involve people a little wide, know everything that mixed but not fine. Many start-up companies need such a technician, when the company started, this type of technology can quickly construct the company's technology system, a combination of technical talent more clearly what the company needs in order to create a complete product, but also some of their own work everything the meaning of. Then other companies on the scale of development, the system is facing greater challenges, we need to recruit technical experts in various fields mentioned above to be responsible for various subsystems inside of a large system.
A combination of
In line with the previous requirements of technical experts, but also eclectic in line with the requirements of the technical aspects of both depth and breadth there. After all, a person's energy is limited, should both have a deep breadth, and sometimes more difficult to achieve, this may require enabling environment and coupled with individual effort and talent. It also said that, for now a lot of people trying to program, to Hunde Hao in the workplace, but also do not need to fight talent, effort enough, ha ha.
2. prioritize
I have seen some of the technical staff, I spent a lot of time to remember some of the principles of non-essential things, and these things will be able to use the time to look up documents found. Of course, you can back down is better, do not check the documents, but the human brain's capacity should be limited, we should make effort to understand and what belongs to the essence of the principle of memory.
There are many possible concrete realization of these principles-based nature, we can quickly understand if we understand the nature of the principle, later met a variety of concrete reality. Otherwise, the concrete implementation has changed, you have to remember it, but the specific implementation varied, how can you remember the finish. Therefore, we should seize the essence of principle, understand one or two specific implementation like, so that can achieve the effect of maintaining the status quo, the same principle is the essence of the change is the implementation.
3. apply their knowledge
I have many years of study, I did not pay attention to apply their knowledge, which is why I understand what a pain. I had to learn a variety of theoretical knowledge, then feel superior, but these things in my work basically do not have access, but over time, these theories have faded from my memory, when I when they met again, only the feeling of deja vu, but has been unable to understand the principle or idea.
While others, because of the needs of the business scene, dig some technical aspects of the application up to the system level and even to the hardware layer. This method of learning is on-demand learning, learning can be considered based on usage scenarios, any technology is to solve the problems in certain usage scenarios that occur. Because the actual usage scenarios, the effect of this would be much better learning and memory will be deeper, it is a way of learning I am currently relatively advocated.
4. Theory and Practice
When you feel difficult to understand abstract theoretical knowledge, hands may need to practice in order to deepen understanding, and practice when you feel no idea, probably need to replenish the theoretical knowledge. Therefore, the theory and practice always complement each other. Practice without theory is like a tree without roots, no theory of practice is like castles in the air.
以我自身的经历来说，我曾经花很多时间去学习一些自己暂时用不到的技术框架，网上的各种文章都看，而且感觉文章一篇写得比一篇好，貌似自己收获很大。然而因为没有实践，我对很多概念一知半解，直到我们项目亲自需要使用的时候，我才亲自用那种架构方式去搭建系统。当我搭建完系统后，我才发现，我根本不需要花那么多时间去看别人的文章，如果我没有亲自去搭建，可能我还会再花很多时间去看类似的文章，却可能永远达不到深刻理解的程度。
因此，技术是实践出真知的，有时候真的是：干就完了，否则，你会有类似这种困惑 – 为嘛听过无数的道理，依然过不好这一生？
5. 跳槽的问题
说起跳槽，我们几乎都不陌生，而技术人员流动性相比其它工种的人士更强。网上很多人都谈论过这个话题，在这里我还是不能免俗地要抛出自己的见解。
我认为，职场初期，适当花心是可以的。因为这个阶段的我们，往往不太清楚自己到底想做什么，适合做什么。这样的话，就需要更多的尝试，尝试不同的岗位，如果能有幸找到自己感兴趣的岗位，那么基本就是值得自己今后多年精力投入的方向了，你要知道，职场上太多人，只是为了谋生而从事一份工作，根本做不到乐在其中。
当你找到自己的方向后，建议沉淀下来，从技术、行业业务角度去构建自己的核心竞争力。这种情况下，如果其他方面问题不大，不建议频繁跳槽，最好在一个公司多呆几年，学到如何开发产品、如何运维系统、如果运营产品等知识。
6. 格局的问题
很多年前，有个在代码界略有名气的人在网上说，刚开始他觉得是数学限制了自己的发展，后来觉得是英语限制了自己的发展，再后来发现，其实那些都不是事，真正限制自己发展的，是自己的视野，也是格局。
我也是比较赞同这个观点的，你能想象一个每天只默默耕种自己那一亩三分地的人，能够去开疆扩土搞大事情吗？因此作为技术人，想要不断地成长，同样需要多关注技术发展趋势，大的方面不说，起码对自己所使用技术栈过去发展历程和未来可能的发展方向有一点点了解，大概了解技术的演变史，这样对自己的技术选择可能会有些帮助。
These are my heart for so many years fought Lek summary, frankly, some of these aspects, I do not good enough for me, how much pain comprehend. These lessons learned or, summarize the pros and cons worth mentioning, do not necessarily have to help everyone, but maybe you can learn from it, if there was something a little bit of inspiration for you, it would be my pleasure