My 2017 can be described as a failure.
It was a failure on all fronts. The biggest failure at work is the project you are working on. You work hard day and night, and then you get pulled out and transferred to another project. Peach trees have worked hard to plant their own, eager to see others pick peaches. To make clothes for others. Interest is the same thing. I always feel that the biggest shame of a programmer is that his work results are denied and the things he is doing are suddenly not allowed to be done.
It really hit me. And of course it made me reflect:
1. First of all, the relationship with the project manager was not well handled. Regardless of the role defined by the Feature-driven Development approach (FDD), or the actual situation, the project manager should focus on external coordination, and I, as the development manager, should be solely responsible for development management. However, the project manager did not have a clear position and wanted to control everything more and more. I also lacked a clear understanding and failed to make rules and regulations from the very beginning. I also failed to correct the situation in time when it was not good. In fact, this situation should be avoided if timely communication.
2. There is no lead programmer in the personnel structure, and there is a fault in a project team. According to the division of FDD, developers should have development manager, architect, lead programmer and programmer. Development manager and the architect is me, but there is no primary programmer, I also want to act as the work of a programmer, writing the most complicated part of the project, and it, has very little energy to take into account other, this is I the development manager in this project looks not enough good, the last is the biggest cause of lu.
The role of the main programmer is to undertake the development manager, architect, to the programmer, it is easier to understand the requirements of the development manager, design modules, guide the development of programmers, check the work of programmers and so on.
In fact, there is such a person on the team can act as the main process. But he didn’t work for me. He was put together as the project required. His relationship with the project manager was very good, and I was polite, so the project manager bypassing me, the development manager, and gave him the order directly. And I can barely get him to move.
However, this should all be communicated. As long as I insist, and report to the superior, estimate he also dare not not listen. So, the root of the problem is me.
Work is work. Be strong when you need to be strong.
However, this year, I have made progress in GIS development. Through efforts, I have a little understanding of its principles and can make some things.
As a programmer, you should be constantly learning, learning new knowledge, and keeping an eye on new trends in the industry. No matter how the world and the environment change, a high level of professionalism is what a programmer lives for. This is what has become increasingly clear to me in 2017. The idea that programmers are too old to learn and inflexible is bullshit. You deny yourself, refuse to learn, rest on your laurels, that thinking must be rigid. Because of age, seniority and experience, learning is easier to relate by analogy. Of course, when I say experience, I mean principles, not tools.
In 2018, I will continue to adhere to and carry forward. Learning is always on the road, can not stay for a moment.
My 2016