It was cloudy on Friday, December 21, 2018

10 years of development experience

10 years of working experience

10 years as a horse

survival

More than ten years of study, ten years of work, thirty years of existence in the world. Looking back, through the pit, eat losses, can be written in a thick book. I organized my notes into a book, which I think is a much thicker book. Live, the ability to learn or to learn, do things or to do. Only a mouthful of food to eat, a piece of clothing to eat. Learn a trade, raise a family.

Developer’s way

Choose as a developer, as an iOS or Android developer, or some other backend, front-end, etc. So some things, developers do, or do it well.

I. Engineering familiarity

1. Love what you do. Be very familiar with the business. Business and development complement each other, business mastery, development handy. What should not be done should not be done, and what should be done should be intensively cultivated. Can also be in the development, can be forward-looking.
2. When it comes to developing specific businesses, be familiar with all the details, down to a pixel. All business functions and code are clear and clear, and each iteration is clear.
3. All business-related documentation, including code related documentation, is also well documented. That’s no excuse for not having anything to do with me. Prepare for what could be your job later.
4. Documentation of the company’s business, every detail. Read and read deeply. Including development interface documentation, product instructions. If you are a new employee, make sure to do this.
5. Familiarity with code engineering is the most important thing. As a survival skill for development. If you’re new to the job or have a deeper understanding of the project, look up or study the company code if you have time. On the one hand is to improve themselves, on the other hand is for the development of new features, do targeted.
6. Learn from your predecessors. All rivers run into sea.

Ii. Development process

1. Familiarity with requirements specification. It’s the developer’s job to write code, to understand what needs to be done, why it needs to be done, and what the risks are in doing it. So it is necessary to discuss and study the requirements specification. Spend as much time as possible on requirements discussions, sorting out all the details with the product manager.
2. Familiarity with visual drafts. As a front-end and terminal developer, this has to happen. It affects how users feel about using the product, the increase of new users and the retention of existing users. Rely on this attractive interface and humanized detail design. A simple and smooth interface operation experience is the pride of development. Hold good stylist MM so every idea and the aesthetic feeling that every pixel reflects, perfect realization them.
3. Familiarity with original business code. Before starting new feature development, is the code of previous projects familiar, common or common code understood, and code style understood? This directly affects the quality of new functionality, the efficiency of development, and the robustness of code.
4. Preparation of basic knowledge. Does every developer feel confident in his or her code knowledge before he or she starts writing code? Are you familiar with the technology, familiar with the technical knowledge, and thoughtful about the development of new skills? To write beautiful code, preparation is essential.
5. Design of program architecture. We’re all set. Before we roll the code. With proficient business knowledge, know the technical ability of the chest, spend a little time to do a program design. Make the program readable, robust, testability, scalability and so on are guaranteed. The maintenance of that later period, is really a small bridge running water family as wishful.
6. Program self – testing and joint tuning. Good code takes a lot of work. Complete self-testing, the operation of each line of code, the judgment of each condition and the abnormality of each function, is very necessary. A thousand lines of code without a BUG during development, 👍👍👍. Coordinate with the backend or other groups with a collaborative first, document-first mentality. There are rules and regulations. Double the efficiency.
7. BUG fixes. It’s a good sailor’s day to capsize, so be wary of bugs raised by testers. Every BUG fix is an opportunity for developers to grow in experience, and the next time you write perfect code. Active cooperation, rapid modification, comprehensive self-testing, timely version. Keep everything in the hands of the developer.
8. Code review. Submit codes every day, conduct code review conditionally, learn from and supervise each other. It is a rare opportunity for me to improve my code level, communicate with my colleagues and find hidden problems in the code. (Work hard, do what you love)

Three, assessment points

The company is indispensable KPI assessment, always want to come some indicators.

1. Specification of code. Choose a standard specification or the company to determine a specification, we implement together, and constantly improve. Achieve uniform code style.
2. Business functions are understood without error. From requirement review to feature development to release production, the business implementation is faultless.
3. Code level assessment. Code quality, number of bugs during testing, number of bugs online. Are clear and visible indicators of developer value.
4. Online problem repair and timely feedback. It is inevitable that some fish will slip through the net. But the first response, the first fix, is the quality of the developer. Write your own code, you are responsible to the end.

Iv. Cultivation of developers

1. Achieve the integrity and quality of requirements. Hold every detail, every pixel, to perfectly realize the vision of product managers and visual designers. And the abnormal situation on the function of all covered, to the user exquisite enjoyment.
2. Continuous improvement of code quality. Every development, every BUG fix, every bit of knowledge advance. I can put it all in the next code.
3. The improvement of technical level. In addition to code, there is no end to learning new skills or knowledge. Usually on the premise of a complete grasp of the existing knowledge, spend some time in learning Daniel to share, is a shortcut to their own improvement.
4. Development ability of excellence. Empty cup mentality, understanding that the code can never improve. Deep into the underlying knowledge and principles, so that their own blind code can also run as usual.
5. Mental adjustment. Every developer is proud to be there. But the developer is also a member of the company, the free company is good, the development prospect of the developer. In the discussion, communication, analysis and so on, with a low posture, modest, modest attitude to deal with.
6. The road to further education. Read more books read good books. Continuously complete and systematic learning of knowledge points, slowly towards the peak of technology. No matter how fast technology develops, basic knowledge is indispensable.

The path to the workplace

In addition to hard development skills, soft workplace skills are also what developers need to learn. Let’s leave it at that. Because I also in the study, also do not do well. But at least make sure your colleagues want to work with you and want to work with you.

Pull off

No one is perfect. Constant mistakes and corrections are the necessary rhythm of moving forward. I have interviewed many people, and I don’t know whether I am not good enough, or whether the HR of the company chose a bad book. It’s really hard to find the perfect person. Look for startups with fewer people but the best in the industry. Be open to positive corrections. Embrace change. The world is changing so fast that there is no reason to stay the same. (. · ∀ ·) Blue ゙ hi, writing is limited, can’t write a stomach of thoughts, speckles, fragmented.

END

I feel like I’m not writing what I want to write. Let’s just hope that makes sense. May God Steve be with you.

If you have any ideas, please leave a message.