Personal work-"people, Performance and professional ethics"

After reading this article, I was impressed. The importance of division of Labor, said that the division will have to mention the position of the leader, a team must choose a decision-maker, so in the face of big things will be decided, the team leader in the group played a leading role, the leader must according to each member's characteristics of the division of Labor, Only a good division of labor can ensure that the project is completed quickly and well. Division after the completion of the team members of the running-in period, everyone has a person's ideas and thoughts, so in a lot of things may be disputed, this time the leader came forward, the team leader to do a correct decision to appease each member of the mood, so that everyone can not take the mood to work. As a member of this group, I think everyone should also take control of their own small emotions, in a team, as long as everyone can be tolerant of a little, no matter the big things do not create a kind of injury and gas.

I think that there are generally object-oriented programming people, that the most difficult and most headache is the design. A good project, design can account for at least 50% or more. The controversy over design is long-standing, in my opinion, it is determined by the nature of the industry, after all, the software industry is for other industries to serve, so the division, as the experience of the growth of business capacity is gradually greater than the ability to program, therefore, the process of decision-making business or business decision procedure becomes a materialistic and idealistic exchange of fire Although in recent years the business decision project controversy has been drawn to the first, but's forgive forget difficult to eliminate, there are still a lot of people are determined to determine the framework of the project, and then analyze the business supporting the relevant technology ideas, this part of the people, if not the process-oriented era of development, it must be nerdy. The business decision project, the project decision framework, the framework determines the programming language, in the final analysis, the fundamental reason is that the software industry is the service sector. This is fundamental, do not confuse.

The seniority and value of being a programmer is not measured by what you know, but by how much you have done. The two are related, but they are fundamentally different. Your value is how you drive the project forward and how you encourage your team to do the same. In my 15-year development career, I never needed to implement a bubble sorting algorithm and short-chain algorithm. However, I spent thousands of hours writing and refactoring account management tools, editing suites, caching logic, mail interfaces, test suites, deployment scripts, JavaScript layering, analysis architecture and documentation. These are valuable things that have done these things to propel us forward.

The tiny components that build the bricks and gravel of the project require hundreds of hours of hard work to assemble. Although they are used to assemble complex systems, they should not be complex in themselves. You should aim to simplify these components. Over the years, I learned that simplicity can be achieved by taking time to work and refactor, which is much easier than purely "inspirational" thinking.

Simplicity and excellence This is the surest path to continuous improvement through something or anything that can be done and re-examined from the back of the process. That's what companies and MVP are trying to penetrate into our conscious minds, and so is software. Starting with some work-but-ugly solution, you're constantly using this ugly and bizarre scheme to continually refactor it into the simplest form. Simplicity is more reliable than "light flashes" from work. Writing code is more predictable than laborious thinking. Simplicity comes from effort.

Personal work-"people, Performance and professional ethics"