First, the career direction positioning
First, only determine their own career direction, in order to better career planning. In my opinion, do career direction Web front-end technology that can be found are the following:
(1) Senior Web Front End Engineer
This direction can be considered a basic Web front-end choice, in other countries, many foreigners are able to put their expertise to achieve the ultimate, can continue to learn and a lifetime to accumulate in one area of expertise. Mainly in two aspects of internal and external factors, internal factors are usually foreigners and rather straightforward, easy has focused on one area; external environment is good abroad, can a good career path such support.
In Taiwan, from the internal terms, WEB front-end technical staff is still quite impetuous, usually because the update speed of the Web front-end knowledge of the learning curve too fast and think hard, eventually turning back or other road.
From the external terms, Web front-end staff did not get a fair treatment, may begin production from the HTML page and inherited, never WEB front-end staff than the low first-class back-end staff, looks like the front end is the "plain" synonymous with the back-end It is the "esoteric" synonymous, which directly lead to revenue front-end and back-end staff who can not match, while a direct impact on the level of activity of the front end of the job market. On the other hand, the front entry technology more easily, causing the other extreme: the proliferation of personnel, the scarcity of talent.
I want to say to all of WEB front-end engineers: bread is always there, to loneliness! I personally recommend this career direction, because in this direction, as long as the probability sufficient patience paid off, success is very high. At the same time, this is one of the most simple way, we are spending more energy on studying technology, rather than office politics and other trivia.
(2) Senior Web architecture
Say something utilitarian, I like this direction, taking into account both the simple work, but also to reduce the workload of the actual Coding can devote more time to study technology. In the country, Web front-end engineers encountered more cases are always repeatedly write the same code, always facing the same technology and products, easy to feel boring. Since we have the most extensive knowledge of Web precipitation, making it easier for us to become an architect. The career development not as good as the first is more smooth, mainly as an architect had to learn: the back-end technology, DBA, Platform and other content, and this often requires learning the actual surgeon to do the project, not to write two at home like a Demo, which is bound to suffer growing pains for some time. Although not very smooth, but the bigger picture for a good, good understanding, broad knowledge of front-end engineer, I recommend you make an effort to take a glorious architect of the road now.
(3) their own business
In fact, their own business is the best way, is the lowest success rate of road, challenges and opportunities. Here, as a front-end technology staff needs to be more on their vision of dynamic, dynamic industry chain, related products in the field of dynamic industry, the attention to detail to maintain the advantages, while enhancing their own to control a product or even a the company's ability destiny. But this road and road technologies slight differences, follow-up will not repeat them.
(4) management of job transfer or other
Since the road is not the career path and Web front-end technology of the relationship, therefore, there is not too much to discuss, however, whether or not to go down this road, I feel that for any road technology, the better the bigger picture, the broader the vision is a prerequisite for the development of good, has a good vision and a broader perspective there is no alternative but to continue to carry out horizontal expansion and accumulation of knowledge, at the same time, and more time to practice in the horizontal expansion of knowledge, the knowledge into skills.
Second, career goals
I have an ultimate goal, on this goal, we need to give yourself to develop a series of learning and growth plans, methods developed as follows:
First, carding knowledge architecture;
The purpose of that sort of knowledge architecture, we have to understand clearly what technology is the front, which is the successor technology, that technology is the depth and breadth of what technology is, after carding a good knowledge of the schema, as these two dimensions, we can establish a clear and accurate the growth target and efficient growth plans.
Second, target decomposition;
I think, probably be broken down into three stages, including: the initial stage, to enhance the stage, formative stage. These three phases correspond to different objectives:
Infancy:
1, basic knowledge of
在我们梳理的知识架构中，按照我们分析的两个维度里最前置的、最浅显的部分，作为打基础的阶段，必须要在这个过程中更多投入到实践中去，我们通常做的多了、熟练了，就认为这部分知识和内容掌握了。
2、常用工具的掌握
对于常用工具的掌握应该掌握一些有大公司或专业团队背景的流行工具，这些工具的熟练掌握能够提升专业度、职业度，同时，能提升我们的工作效率。我们只有在检验自己对于知识和技能熟练程度的时候，才会自虐式的用Notepad去编写页面、css和脚本等内容。
3、沟通技巧的掌握
通常做技术的人会被定位为“不善沟通”的人，这是为什么呢？究其原因，主要是因为多跟程序和代码打交道，跟人的沟通较少导致。这种时候我们要特别注意增加
和人沟通的机会，着重提升这块儿的能力。另一方面，我们通常被称为“不懂沟通技巧”的人。作为一个技术人员，包括我自己，似乎天生就有一些难以接受挑战的缺陷。在国内，我们的技术人员通常都是自己制定方案、自己执行方案，在执行过程中又缺乏相关产品、交互设计等人员的沟通，大多是在自己的思路贯彻下进行开发，久而久之，我们习惯于信任自己的观点、在自己的视角看问题，对于挑战总是百般地“据理”力争。我们需要更多提升的是，如何在对方的视角看问题、如何在用户的视角看问题。
4、良好的开发习惯
开发习惯是养成的，一旦有不好的习惯，对于将来去修正带来的将是很大的麻烦，我们在培养良好开发习惯一定要从起步时做起，例如：写代码之前先分析、先写文 档、先写注释。定义变量最好能用直接可理解的语义，最好是拼音，别整英文，尤其是生僻单词，将来自己忘了还要开金山词霸。文件最好有有意义的文件夹命名来管理，文件名最好有意义，需要版本号的最好能和项目版本号一同更新……等等。
编程工作第六个年头了，与大家分享一些学习方法，实战开发需要注意的细节。767-273-102 秋裙。从零基础开始怎么样学好前端。看看前辈们是如何在编程的世界里傲然前行！不停更新最新的教程和学习方法（web前端系统学习路线，详细的前端项目实战教学视频），有想学习web前端的，或是转行，或是大学生，还有工作中想提升自己能力的，正在学习的小伙伴欢迎加入。我们会一起结伴同行前端前端前端
提升阶段：
1、高级技术的掌握在提升阶段对于知识和技能掌握，我们需要从梳理好的知识架构中选择更深一层次的技术进行学习，选择之前，我们先通过类比或预估的方法，衡量自身学习的难点，
以学习难点和自己最不感兴趣的部分为主。这样推荐大家的原因是：这个阶段我们兴趣正浓，已经度过了苦涩的起步阶段，到达了兴奋的提升阶段，我们要用兴趣和兴奋去挑战最困难的部分，在我们信心受挫和兴趣浓厚之中找到平衡。同时，辅以其他的深层次知识一起学习和研究。
2、产品思想的学习
没有正确的产品思想，很难设计出良好的程序，无论从界面、交互，还是接口、逻辑，不能够理解产品、理解用户需求，我们会给自己造成很大的麻烦，例如：我们 千辛万苦用最新技术、最复杂的实现做出的功能，却得不到使用者或领导、同事的认可。为了使我们的工作和学习更加有效率、避免无用功，我们需要不断的学习产品的思想，只有理解了产品的思路，我们才知道用我们的技术去输出什么。
3、各种框架的学习
框架是我们提高工作效率的优秀手段，对于框架的学习是成长必经之路。我们学习框架的路线通常应该是：使用——》分析——》个性化定制——》模仿编写自己的框架。只有大量的使用，才能明白设计框架者在设计背后的思路，只有了解到设计的思路，才能做正确全面的分析，只有正确全面的分析才能支撑我们去对其裁剪或 扩展，只有经过实际分析、修改别人的框架，才有可能写出优秀的、自己的框架。学习通常的路线是：学习、理解、模仿、创造。
4、富客户端应用的学习
随着带宽和计算机性能的提升，以及Web2.0的如火如荼，富客户端应用充斥着互联网，如果你不懂得富客户端应用，你就不能称之为一个合格的前端技术人员。可以按照：Flash动画—>Flash编程—>Flex—>Air—>Silverlight动画—Silverlight编程 的步骤学习，先学Flash后学Siverlight的原因，一来Silverlight还不太成熟，二来，实际Silverlight借鉴了很多Flash的思想，最好在学习的时候不要本末倒置。
5、各种网络协议的学习
Web前端技术就是云上的技术，云的协议有N种，我们应该着重学习：TCP/IP，UDP，HTTP，POP3，SMTP这几种协议，在开发Web前端应用过程中，这些协议是我们的技术的载体，有时候决定了我们的应用是否能实现、有时候决定了我们的应用是否高性能，同时，这些协议还是我们和后端技术交互的 重要手段，这些协议就像是密码字典，帮助我们把后端传输过来的密文解释成我们前端技术能够理解的明文。
6、程序设计
这个阶段我们需要学习OO、UML、设计模式、设计方法……，我们要让技术开发工作变成有目的性、有计划性，并且，这些目的和计划必须有理论的支持，这样，我们设计出来的程序才能够更优秀、我们的开发才更有效率，这样，我们的技术才能有所提升。为什么要学习程序设计呢？主要是，就算我们不用Flash的ActionScript编写程序的前端逻辑，我们至少要把我们自己的Javascript函数、包的定义规划起来，避免将来自己或他人维护代码的时候出现问题。程序设计能力，在技术人员仍然被看作是程序员的这个年代，是灰常、灰常重要滴。
成型阶段：
到了这个阶段，我也没什么好说的了，如果能达到这个阶段，就证明后续的成长之路是异彩纷呈的，是成为一个资深Web前端工程师，还是成为一个资深Web架构师，亦或其他，都要具体分析自身的特点和兴趣所在。如果是资深的前端工程师，我觉得更重要的是去作新技术的研究，互联网技术发展速度日新月异，不断学习新技术，否则就被淘汰。此外，我建议在知识的广度、深度方面最好能挑选一个自己最擅长和最感兴趣的一两个领域深入钻研，不要挑太多，多而不精。如果是资深的Web架构师之路，我建议要深入了解后台技术，这种深入了解一定要伴随着实际的项目开发，基本方法是：按照别人设计的架构实现几个Server—>自己设计并实现几个Server。