2016 re-sail to commemorate my lost programmer career

Watch the time leap from 2015 to 2016, listen to the bell that represents the arrival of 2016, heart filled with emotion, time

Hurriedly, suddenly look back, not aware of oneself has become a 5 years old (not the school's code age) of the small senior programmer.

On this New Year's Eve, in this fireworks in the night, write down my 5 years of programmer life, in order to commemorate my lost green

In the spring years, I remember the programmer's life that I tapped at my fingertips.

In 2011, with the arrival of the graduation season, I came to my current internship in this company. Yes, I'm in this company now, and I'm in our

The company has been around for 5 years (I should be able to be rated one of the most loyal employees in our company). Started my programmer's life, just

Into the workplace, as a rookie, as a novice programmer. The profession of programmers is full of novelty, full of fantasy. Then the

I was like a sponge to learn, with the attitude of the mountain back to learn the company's technical structure, reading the code of the predecessor. With humility

Attitude every day with the company's so-called veteran programmers follow the back of their way. In the mood of worship listen to them tell me what they do

Over the classic project. Then I started to be like chicken blood every day to develop a small function assigned to me by the group leader. Although the task is very small, but

It's enough to get me excited. In fact, my main task at that time was to copy the code of the predecessor and then the transformation. Take my team leader.

Give me the task of the time will always tell me can refer to a function to write. Then I'm going to copy someone else's code and make a makeover. Even

So, every time I complete a small function of development, still let me have a full sense of accomplishment. It is this sense of accomplishment that inspires me to lead

I step-by-step on the road to programming, now think about that year my job is to copy someone else's code, and then change, then copy and then

Reform. But every day is full.

2012, I am still doing development, but I have started to independently responsible for the development of modules, I began to find that the code written by predecessors and

It's not as perfect as I thought it would be. found that their code also has bugs and flaws. I began to try to write my own tool class.

This year I went through a project from No to go on the whole process, experienced the programmer's crazy overtime, experienced debugging a bug to deep

The night when finally debugging success after the kind of joy. At that time, in order to debug a bug in the company overnight overtime, not for the other is because

The bug does not solve the home also can not sleep. There is the kind of resolution that this bug does not resolve. I think I was really in love with the program.

The job of a member. There is also a heart that a programmer should have to endure loneliness.

2013, I took over a system of operation and maintenance work, should not be said to be operational, because the system's business has been changing. So

Development tasks are available almost every quarter. My task is to be responsible for the normal operation of the system. So I started looking at the system.

Architecture, I began to focus on the stability of the system, the security of the system, the operating efficiency of the system. And start refactoring some functional modules to make the system

More robust to run. During the year, I was involved in almost all phases of the project development process, writing requirements documents, detailed design documentation,

Do design, coding, testing. Responsible for the system on-line. Remember the first time and business talk about the mood of the need, remember the late night on-line small

Heart Wing Wing. 2013 I can certainly discard the rookie programmer's title.

2014, the opportunity to join another project team to do an online mall project. As a core member of the project team, participated in the

Project system architecture, table structure design, technical research. In this process I distinctly feel the inadequacy of my experience and the short board of Technology. System of

Architecture and system table structure design is the soul of a system, will directly determine the success or failure of the project. As a system architect,

Need a wealth of industry experience, is the need to have a deep understanding of the business of the system used technology has a strong practical experience, only the possession of these

To build a good system architecture. The deepest sentiment is that they do not know a lot, they need to learn a lot of knowledge.

2015, quietly I seem to be a veteran of the programmer, I have their own team, began to take my team small projects. I can

To manage my team according to the management idea, I can build my own team according to my own idea. began to draw a pie for my crew, to inspire

They write code like Chicken blood. From them I seem to have seen myself in that year. I think I've done it from rookie programmer to old

The evolution of the bird programmer.

2016, whether I like it or not, whether I want to or not, it has quietly come, 2016 re-sail, I want to self-

said, adhere to their own beginner's mind do forever things. Stick to the passion of programming art, do the programmer forever.

2016 re-sail to commemorate my lost programmer career