15 Top career recommendations for future programmers _ programmers

Well, the code brother thinks 10 is not enough, there should be 15 career advice. or 100 bars. But first, I want to explain what a good career is like.

Their progressive curve is not a straight figure that rises a little every month. (That is, ordinary people's careers will not be such a straight line graphics.) Each month to improve a little, and then quantitative change to achieve qualitative change, there is a big progress. ）

A great career looks more like this. In a certain period of time growth slowed down, and then after the "bottleneck" there will be a sharp rise.

Why there is a change in color. That's because careers have changed: software development to product management, sales to co-founder, and so on.

There will also be some setbacks. The reason you also know, want to achieve greatness, must take a certain risk. And enough risk means you're going to fail.

So, that means ...

First, the code:

1: Write code. Write a lot of code. The school is very good at imparting theoretical knowledge, but is not good at teaching some practical things. This is particularly true in first-class universities. Professors are also academics, often hostile to more "practical" forms of education. The best way to be a great programmer is to practice-lots and lots of practice. The content you encode (open source, IPhone app, etc.) doesn't matter much, as long as you're coding and progressing.

2: Not dependent on the language. Language is just a tool. It is valuable to know a language in depth, but it is also valuable to learn something new. The best developers tend not to be labeled by __ developers.

Second, Occupation choice:

3: "Fox" false Fomesafen. Writing your resume in your CV helps to attract attention and give you an opportunity to show your strength. If you can get opportunities like Google, Facebook, Amazon, Microsoft, Dropbox and so on, be sure to grab it. (But don't stay for a long time, for reasons see #4).

4: Quickly leave the large company. If you want to build your career in a big company, you can stay there by all means. However, if this is not what you want, then please leave quickly. After graduating from college, there is a year or two of working experience similar to Google. Stay for 10 years. There's no need for that long. Although you can continue to learn something, but the harvest will decrease with time. (unless you want to be a member of a big company.) ）

5: If you want a + career, then please come to the San Francisco Bay Area. I love Seattle and I started my career here, but I have to tell the truth: there are so many High-tech opportunities in the Gulf region. If you are somewhere else, then you can only frame yourself as an engineer (or a product Manager/technical business role).

6: If you don't want a A + career, don't come to the Gulf. Because the standard of living here is extremely high. I'm serious. If you want to have a lot of career options, it's worth it. But if you're just looking for a cushy career, it's better to go to other, more affordable cities like Seattle. The pay of a good software engineer can buy a nice house in Seattle. It is an extension of the Gulf.

7: If you don't want to be a developer forever, move fast. It is valuable to have a thorough understanding of technical expertise. But it doesn't matter whether you've spent two years or seven years to become a developer. Within a few years after graduating from college, make your choice. You want to be an engineer for the next 10,20,30 years or a career change. If you don't want to stay in the same job all the time, then you can start trying to move on. The engineers will not be able to help you much longer.

8: Swift resignation. Walking through my friends who have changed jobs, almost everyone has had a "resignation" in the past 6–12 months. Some people still stay for 2 or 3 years after they say they want to resign. They waste so much time because they are unwilling to change their mentality of procrastination. If you want to resign, start taking action now.

Third, dealing with others:

9: Integrity and honesty. If you cheat and cut corners, you will suffer. To do the right thing in life. This refers not only to doing good things, but also to doing smart things. So that people will trust you more and like you. There will be more doors open to you--these doors may be a critical moment in your career breakthrough.

10: Willing to help others. If possible, help those who seek help. This is a good thing, and it is a wise man's approach. Those who ask you for help are more likely to give you help in the future. This "help" may be the introduction of you to the people who are more able to help you directly. So, even if you don't feel that this person will help you, maybe his buddies can or will help you in the future.

11: Make friends. In fact, it is impossible to really succeed on your own. If you're an entrepreneur, you need to be a bridge between employees and businesses. If you are an employee, you need a job. Either way, friends are the key to opening up these opportunities. Being friends, far or near, makes up an important part of your network, not the strangers you meet at the party and never talk to.

Four, want to become a cow person:

12: Knowing--literally knowing yourself internally--gets the fake syndrome. Even the most successful entrepreneurs and engineers (except for a handful) feel that their success is simply because they are lucky not to think they are as good as everyone else because they have a "fake syndrome". Recognize that the general of the Imposter syndrome can make you realize that you think you are a qishidaoming, but not really.

13: Starting from now. Show your positive initiative. Opportunity waits for no man. Looking for new opportunities. From now on, it can be a programming marathon, a club, a startup project, a start-up, a new running group, and so on. While doing these things, you will learn a lot to help you open up the doors of opportunities.

14: Take risks. Seize the opportunity. When you notice a looming opportunity, be sure to catch it. Look where it's going. Don't just ignore it because you don't know exactly where it's going.

15: In favor of "yes". Great business is in the "breakthrough" moment. The problem is that you don't usually recognize those breakthroughs in advance. You don't know what the point of this meeting is, then you don't know where it will go. You never know, two months from now, this person will introduce you to a guy who needs some advice and eventually becomes your business partner. Insist on being biased towards saying yes.

All of this is justified-usually with multiple stories behind them. These stories are from me, or my friends/clients, personally experienced.

Coding a number of many items (1), plus some friend's recommendation (11), led me to a freshman, to be able to intern at Microsoft.
This set the foundation for my successful hiring by Google (3), opening the door to countless opportunities.
Being active (13) and grasping opportunities (14) rather than careful planning and research so that I can start two companies, both are profitable, and let me accumulate amazing experience.
In fact, the two companies started out as an unpredictable consequence of agreeing (15) to help Friends (10).
The Purchase consultation (now the core part of my business) started because someone asked me to help them. I didn't really like it at the time, but I still said yes (15) because I knew very well how valuable the idea was.

Five, I also make mistakes:

I like Seattle (where I used to live), but the gulf is more conducive to my career. There are more opportunities and better opportunities for development (5). Although the level of consumption here is much higher (6), if you are not going to take advantage of those opportunities, go somewhere else.
I may be spending a lot of time at Google. The extra time does not allow me to get too much (4). I finally left because I realized I didn't want to be a developer (7) and I was unhappy (8).

In addition, there are two suggestions that we cannot ignore.

There is a lot of flexibility in the use of language, and there are no hard rules. Once confined to a language, his career is limited (2). Developers who are specific to a particular language tend to be stigmatized as worse and have fewer businesses to choose from.
When it comes to honesty (9), two stories come to mind. In both cases, a person's desire for success causes them to end up hurting themselves.

In the first case, one of my colleagues tried to exploit a legal loophole to support a very important delegate. Although he finally made a concession, I decided not to cooperate with him again. I will not give him any help in terms of trust. (That is, I will help him write the investigation report, but will not help him contact anyone.) ）

In the second case, a fellow writer wrote me some false negative comments. When I confronted him, he fabricated all kinds of lies and charges. Now, he regularly asks me to contact someone I know, or ask if I want to work with him on something. I turned it down. Again, this is not revenge, I just want to protect myself and my friends.

Read here, do not know if you have noticed, there is another leak, that is: the fake syndrome (12).

I have known about the fake syndrome for many years, but it was not until the last year or two that I have found that almost every successful person has experienced it. So, feeling that you're not good enough may not be the truth. By recognizing this, I have more confidence to post something (13), try to seize the opportunity (14), or say Yes (15)

What are the pieces of career advice ... software engineers?