Original article: http://haoel.blog.51cto.com/313033/124600 life is short, belong to their own gold time is not much, if too much time wasted in looking for the road and direction, very
This may cause nothing to happen. You need to determine your plan as soon as possible, and then follow this plan unswervingly. There are two most important aspects during planning: First, you can clearly understand your abilities and advantages.
And personality; second, determine your own major and want to engage in the industry. You can make your career plans only after determining these two aspects.
It is not easy to know yourself.
We should examine and understand ourselves from the following fifteen aspects to help us establish our life rules.
TIPS: a) Knowledge
(B) problem solving, judgment, and analysis capabilities; (c) Handling of difficulties
, D) teamwork, e) Presentation and language organization skills
, F) creation and innovation
Force, g) communication skills, h) introverted or extroverted personality, I) Are there any perseverance in research? J) weaknesses and personality defects, K) ability to learn and acquire knowledge
, L) lead
Organization capability, m) enterprises that can currently enter
, N) Current position in society, O) current competitive strength.
Career planning is like Software Engineering
After determining your own industry and professional fields, the next thing should be 1)
Strive to master the knowledge of this industry
, 2) learn more about this major and industry in the shortest time
Subdirection
. Then
Re-recognize yourself in the process. For example, if you select the computer industry, you should try to work in different directions in the computer industry, such as software, hardware, network, entertainment, and media.
EB, system, item
Project, ERP, CRM, database, embedded
...
..., Development, testing, technical support,
Process management, project management, system architecture
, Pre-sales, after-sales .......
In this process, confused exploration may be difficult to avoid. It may be a shortcut to get guidance from the predecessors in a timely manner. Asking for advice from the predecessors can serve as a reference. A quick prototype (quick try) may also be
A good way.
Always
Jump out and check yourself again
, Objective analysis
Your own strengths and weaknesses
. Let yourself and others know how many pounds you have, learn your strengths and characteristics, and then you can know what you are suitable.
It is an evolutionary process of "affirmation to negation to affirmation" and adjusting your career route. After a period of "Strangeness" to the society, you can talk about your own life and career.
Plan.
Personal career planning is like software engineering. We all know that the biggest enemy of software projects is unclear requirements and large-scale changes in requirements. Similarly, in personal career planning, self-defined requirements and changes in requirements
It is also very dangerous, especially when the career plan implements changes and changes in demand after year 45. Only
Requirement Determination
Later, we can talk about the HLD (high level
Design) and LLD (low leave
Design), and the specific implementation. Since then, as you become increasingly mature, you can fix your own bugs at any time.
Patch
(Patch)
Improvement
Your own career
Design and Implementation
Detailed rules
(Enhancement) and add
More and stronger capabilities
(New feature requirement ). The software version is upgraded.
8-point suggestions for new programmers
Hard to read
I began to read and study hard. In the first year I went to Shanghai, I read four or fifty books.
PB,
Delphi, SQL, HTML, CSS, DHTML, Java, Perl, CGI, ASP, PHP, JSP, XML,
UML, MFC, Lotus Notes, UNIX, Oracle, Informix, C ++, ActiveX, ODBC, ADO,
. Net, COM,
And even
Cisco
Vro configuration,
Photoshop, 3 DMAX
...... "I read a lot of books and didn't think about the direction I should take. I don't know whether it is good or not ." Maybe there are too many books and too many things to understand. Later, I had the opportunity to participate in a national project. Background is
AIX + Informix
Use
C
Development, front-end is used
PB
Of
PFC
Interface, through
IBM
Of
CICs
This middleware connects to the front and back ends. During the one year of project development, Chen Hao
UNIX/C ++
And distributed systems have a deep understanding, and are deeply fascinated by them, while they have a deep understanding of the process and management of large-scale software engineering. This project has a great impact on Chen Hao. In addition to technical gains, Chen Hao has gradually determined his own plans.
Outside of Technology
2002
At the end of the year, a company in Beijing was engaged in distributed computing.
/
The Canadian company of the grid computing platform is interested in me.
5
Round of interview, Chen Hao got it
Offer
Again, I started my journey-from Shanghai to Beijing. The new company asked Chen Hao
UNIX/C ++
It has been greatly consolidated. "This company has also taught me a lot, especially my understanding and ideas ." Especially when leading
Team
For European users of the company
Customer Service
During his work, Chen Hao learned a lot.
The knowledge of customer management, English proficiency, ability to communicate with people, and understanding of software have been completely improved.
. Start to think about the problem in a completely different way than before.
--
Think about the problem from the user's perspective
. "At this time, the technical direction is no longer important to me, and the technology has become very simple for me, because the technology can be obtained only by reading a document ." Start to think about how to manage a team, how to create a successful software, and how to manage customers in a brand new way. There are further career rules.
--
Become a successful technical director, build a successful team, and develop a successful software product.
8-point suggestions for new programmers
The rules of life are very important. We should plan well from college.
The following eight suggestions are provided:
1.
When you are in college, try to enter the company as much as possible to participate in practical work. On the one hand, you have accumulated work experience, and on the other hand, you know your work and yourself in advance, so that you can grasp your own direction more accurately during graduation. 2.
From graduation to graduation at least
5
During the year, dedicated technical research is a process of accumulation. do not focus on money and positions. Money and positions are only accessories of capabilities. Do not make money and positions overwhelming. 3.
After graduation
3
Year to year
7
At the time of the year, pay attention to the methods and related management and processes in the work, not only need to know its own, but also its own. 4.
30
Learn from each other in a down-to-earth manner before the age. Learn Technology, learn to be human, and learn to do things.
30
Let's talk about our development after the age of years. 5.
Before graduation
5
Years of accumulation mainly involve the accumulation of data and the accumulation of knowledge and methods. After graduation
5
To
10
The year is mainly a qualitative change and should focus on the update of thinking and peacekeeping ideas. In the next five years, we should have a strong ability to tolerate and accept new things. Never be too stubborn or stick to your own ideas. 6.
For a new job, the previous job will become a foundation for the subsequent work, and the subsequent work will become a natural continuation of the previous work. 7.
Do not focus only on technology. Technology is
Hard skill
It will be mastered as long as it is necessary. More attention should be paid to communicating with people and other personnel
Soft skill
.
Hard skill
Like the root of a big tree
Soft skill
It is like the branches of a big tree. The roots are your foundation, allowing you to stand very stable, and the branches and leaves allow you to stretch to the sky for development. 8.
For programmers, we should always remember that technology is not the main thing, but what problems can be solved through technology. What problems must be solved frequently, what needs should be met, and what technologies should be used.
