10 Essential Habits Every Programmer Should Adopt

1. Rely on official documentation when adopting a new tech stack

When introducing new libraries or middleware, always consult the official documentation, as online articles can be unreliable and may lead to incorrect practices, such as using outdated JUnit annotations.

For example, when unit testing SpringBoot2 code with JUnit 5, the official docs state that the @RunWith(SpringRunner.class) annotation is unnecessary.

2. Test thoroughly before delivering code

Reliability in the workplace comes from delivering products with few bugs, which are evaluated by others, not just yourself. Even if the code isn’t perfect, self‑testing and fixing issues before submission builds a strong reputation.

3. Log inputs, outputs, and execution time

Logging helps locate logical and performance problems. By printing input and output data, you can quickly match business rules to identify issues, and timing information aids performance analysis and alerting.

4. Master Git

Effective use of Git prevents unnecessary bugs caused by merges or version upgrades. A highly‑rated open‑source Git handbook, authored by a GitHub employee, covers common practices, underlying principles, and version‑control strategies for various scenarios.

5. Prioritize functionality over premature optimization

Focus on delivering working features first; optimize only after understanding real usage patterns and performance requirements.

6. Implement clear requirements before ambiguous ones

Develop well‑defined features first, then discuss vague requirements with product managers to reduce communication difficulty.

7. Proactively identify project problems and propose solutions

Finding and solving issues during development creates momentum for the project and benefits the developer.

8. Allocate buffer time in development schedules

Unexpected changes—such as shifting requirements, team turnover, optimistic estimates, legacy code modifications, or cross‑team collaboration—necessitate reserving extra time, which is not idle time but a safety margin.

9. Turn learning into code practice

Simply reading books can give a false sense of mastery; implementing interesting technologies in code solidifies understanding and reveals practical considerations.

10. Improve English proficiency

Most technical innovations and official documentation are in English; good English skills enable access to cutting‑edge resources, such as Kubernetes, and facilitate contributions like translating technical books.