iOS programmers should get rid of the 36 bad habits that affect your promotion and salary!

Objective:

Technology companies in the IT industry have been struggling to track down the legendary inordinately of super programmers, and the latest research shows that there really is such a handful of highly efficient "program King", but how can a normal program ape be transformed into code king?

The below summarizes the 36 vices that lead to the inefficiency of the program ape, which affects the promotion of a raise, and is generally categorized as code organization, team work, code writing, testing and maintenance.

First, the Code organization

1, always say "one will fix", but never cash, procrastination late. Lack of task management and time management skills.

2, adhere to the so-called efficient, elegant "line of code Flow", in fact, readability is the most important, smart is the second.

3, meaningless optimization or over-optimization. (Optimizations like page size are done at the end)

4, do not pay attention to code style and style of rigorous, as far as possible and their own team to maintain the same style, team code style is not good suggestions in time to put forward their suggestions. The transfer of other people's code when think others write a lump of excrement, and then write their own another piece of excrement!

As a developer, there is a learning atmosphere with a communication circle that is particularly important this is my iOS communication group: 638302184, whether you are small white or Daniel Welcome to settle, share bat, a inside questions, interview experience, discuss technology, we exchange learning and growth!
5, the use of meaningless naming, prohibit any A, B, c variables appear, magic value resolutely oppose!

6. Ignoring proven best practices (such as code auditing, TDD, QA, automated deployment, etc.), it is not unusual to use the AOP approach provided by spring MVC to intercept, regardless of performance and code readability.

7, bury their own thunder. (for example, use a library with no errors or ignore exceptions)

Second, team work

8. Premature abandonment of the plan.

9, adhere to an invalid plan.

10, always fight alone. (You must force yourself to share your progress and ideas with your team, avoid illusions, and improve efficiency)

11, refuse to write bad code. (When the schedule is tight, you can write "bad" code, which is the programmer's ability, not the bug, and of course, when you have time to repay the "technical debt")

12, complaining about others, think that others are vegetable chickens, with emotional and communication with each other.

13, do not share with the team learned.

14, to the supervisor/customer feedback speed too slow, can not be timely initiative.

15, will not make full use of Google. Everyone is very busy, no one will be obliged to help you, have problems try to solve their own first.

16, value the personal coding style, think their code style is the most awesome,

17. Take personal emotion to look at other people's comments and comments on their own code. Code review often do not accept the advice of others humbly.

Third, write code

18, do not understand the optimization strategy, written code can only be run, completely regardless of performance and robustness.

19. Use the wrong tool.

20, not the pursuit of development tools and IDE mastery.

21, ignore the error message. The robustness of the code is not considered at all.

22, infatuated with the development of hand tools. (Different types of development tasks need to match the best development tools, such as sublime for dynamic languages, and idea for Java, if you like Vim, doesn't mean you can do everything with these tools) but try to be consistent with other members of the team, such as people using idea, You still use eclipse, and of course you can persuade them to use eclipe or not.

23, do not pay attention to the configuration of the value of the code. (The habit of separating the active parts of the code will lead to a surge in technical debt)

24, like to reinvent the wheel. Do the programmers who work overtime until 11 o'clock in the evening are repeating the wheel?

25, blindly cut/paste code.

26, to deal with errands, superficial understanding, do not spend time to understand the mechanism of project operation.

27, self-written code over confidence. The transfer of other people's code when think others write a lump of excrement, and then write their own another piece of excrement!

28. Do not consider the "side effects" of each design, scheme, or code base. A successful use case does not mean a "panacea" to start from your own business.

29. Stuck in one place but insisted on not crying for help. (Think you are handsome!) ）

Iv. Testing and Maintenance

30, only to write the test can pass, will not write unit tests or do not focus on writing unit tests.

31. Performance testing is ignored in important projects.

32, not to verify whether the code is really available, did not develop the habit of rapid testing in time.

33, major changes delayed push.

34, abandon and evade their own code.

35, ignoring other non-functional requirements. (such as security and performance, prepare a checklist for this, ignoring all of your results)

36, lack of motivation to learn, not lifelong learning, time is long, not keep up with the development of new technologies, will be eliminated accordingly.

iOS programmers should get rid of the 36 bad habits that affect your promotion and salary!