On the self-cultivation of a qualified programmer

01. Be able to solve problems

I think that as a qualified programmer, you must first have Ability is to solve problems "in stages".

The so-called stages refer to junior programmers solving elementary problems, intermediate programmers solving intermediate problems, and senior programmers solving advanced problems.

I remember a friend asked a question on Knowledge Planet and said, "Second brother, I have less than 1 year of work experience. My boss always asks me to look at the source code to solve problems. I can't see what's going on. Any good suggestions?"

I can only comfort this friend and say, "Your leader is not a competent leader." Looking at the source code is a good thing, there is no doubt about it, but if Forcing programmers with less than one year of work experience to read the source code and solve problems is a pushover - except for those with extraordinary talents.

To be honest, in my more than 8 years of career, I have rarely solved problems by looking at the source code. Of course, you can accuse me of not being a good programmer, and I accept that, because my primary goal is to be a qualified programmer.

　Qualified programmers have their own means to solve problems. For example, my method is:

　　1) Find a girl.

　　2) Find Google.

　　3) Ask questions in the Blog Park question community.

　　4) Ask questions in the CSDN forum.

　　5) Ask questions on Stack Overflow.

　　6) Ask colleagues for help.

　　7) Ask the leader for help.

　　8) Ask questions in the Daniel group.

If you really can’t solve it, don’t stay up all night and cry to the sky. Go home and have a solid sleep. Maybe you will come up with a solution early the next morning.

You may think what I say is very mysterious, but I often have this feeling. When I open my eyes the next day, suddenly there is something called "Answer" slowly falling from the ceiling. Come down, and then I stretched out my hands to catch it.

How to explain this feeling? I can't tell clearly, but there is an English word that seems to explain it - "epiphany", which in Chinese means "epiphany", which I like to call "apocalypse" (inspired by X-Men).

It can be said that in the past 8 years, I have not encountered a problem that cannot be solved (that’s how I swear). As I grow older and improve my technical skills, reading source code is no longer as painful as when I was young - gradually, reading source code has become my last resort in solving problems.

02. A heart that is not "glass"

I have to admit that when I was young, my heart was very, very "glass" ". Taking myself as an example is really out of necessity.

Putting the time back to 7 years ago, I was still working for a Japanese company in Suzhou. Once, a member of the team used = instead of == when using if to make conditional judgments, which caused a serious bug in the program. As a Team Leader, I did not detect it during review and testing. This "shady" bug.

The leader was on a business trip in Japan and was scolded by the Japanese. And I was scolded by the leader on the overseas phone call. I was so angry that I hid in the toilet and burst into tears, accompanied by uncontrollable sobbing.

The scene at that time is still fresh in my memory.

Thinking about it now, there is really nothing to cry about. I do bear a certain amount of responsibility. It is normal for me to be scolded by the leader to vent my anger. But at that time, my "glass heart" couldn't stand the criticism, and after crying, I still wanted to change departments.

I advise you not to laugh.

When we first enter the workplace, the probability of us not being reprimanded in public by our leaders is almost zero. If the glass heart acts at this time, it will almost ruin our careers. I'm glad I didn't change departments at that time, because my boss even treated me to a big meal when he came back from a business trip. Later, he even took care of me when he got a salary increase.

As a programmer, we must know how to laugh at ourselves, make fun of ourselves, and release our own pressure. I now feel that programmers who dare to call themselves "code farmers" and "IT migrant workers" are particularly cute and special. Have courage.

If it were me now, and I was reprimanded by the leader for missing =, I would dare to say unscrupulously: "Master leader, please calm down! Write a bug. Xiao Wang didn't mean it. I will change it now and release a version immediately; in addition, I will be more careful the next time I review."

The leader may even be amused. You see, it would be nice if you didn’t have a glass heart.

03. Be willing to share

First of all, let me talk about the reasons why I am willing to share:

　●As a summary of knowledge

　●As a memo

　●Want to help others

　●Build a personal brand

To be honest, I have shared hundreds of articles, but these articles have not brought me direct monetary benefits. The reason why I am still persisting is because I think that one day in the future, I may earn some money from this; if not, I have already sublimated myself in the process of sharing.

The reason why many programmers dare not share is also very simple:

●The big cow has already shared it

●Will you be criticized if you share it

●●The technical depth is not enough

●●The words do not express what I mean

●●There is nothing to share

To be honest, in the first three years of my programming career, I also Never share. The reasons are nothing more than the ones listed above. But when I returned to Luoyang from Suzhou, I had a lot of free time. During the period before I started sharing, I only played games and read game guides. When I got tired of playing games, I felt that life was boring.

I really didn’t know what to do, so I started reading. After reading the book, I felt like I wanted to say something, so I started sharing my reading notes on my blog. After writing for a while, there were still people reading and commenting. In addition, the company also began to encourage blogging (performance award), so I shared the painful journey of solving bugs at work.

As I continued writing, I discovered a huge advantage: some bugs actually reappeared ten days and a half later to scare me, but they didn’t scare me anymore because I had already remembered the previous solutions. Once you're down, follow the pictures and you'll be done easily. You no longer have to look for solutions again, saving a lot of time.

I keep writing and writing, and I find that my writing level has also improved (you can look through the articles I wrote before and feel the gap between before and now). The so-called output forces input, and technical skills It is also more solid, and the knowledge base for solving problems is also richer. It would be even better if the royalties could be more.

04. Finally

I am an extremely ordinary programmer, barely qualified, but compared with excellent programmers, I'm really ashamed of myself.

Recommended tutorial: HTML introductory video tutorial##　MySQL database introductory video tutorial　PHP introductory video tutorial

The above is the detailed content of On the self-cultivation of a qualified programmer. For more information, please follow other related articles on the PHP Chinese website!