How to Become a 100‑Point Programmer: Saying Yes, Saying No, Building a Knowledge System, and Practicing Good Habits

Be Cautious About Saying Yes – Before committing to a task, fully understand the requirements, workload, and team expectations; ask many “why” questions, clarify with colleagues and leaders, and only then agree to take on the work.

Be Bold About Saying No

When faced with unreasonable demands, prepare solid reasons and politely refuse; avoid saying No frequently, but when you do, be clear and address the core issues, communicating with leadership to gain support.

Build Your Own Knowledge System

In an era of information overload, create a structured knowledge framework using a wiki or knowledge‑management tool, categorizing soft skills, architecture, languages, front‑end, back‑end, etc., and regularly consolidate what you learn to form a lasting knowledge base.

Cultivate a Big‑Picture View

Don’t limit yourself to a narrow task; regularly review the team’s overall progress, software architecture, and documentation to understand why products are designed a certain way and why leadership makes specific plans, which benefits career development.

Code Standards

Adopt existing company coding standards or establish your own, covering everything from variable naming to module division; follow authoritative resources such as "Code Complete" and maintain a consistent style without endless debates.

Code Review

Encourage regular code reviews—both receiving and giving feedback—to gain insights, share ideas, and improve code quality; make it a habit within the team regardless of formal processes.

Learn Business Knowledge

Beyond technical expertise, understand the business domain to communicate effectively with product teams, design better solutions, and increase your value within the organization.

Persistence

Develop good habits through consistent practice; short‑term enthusiasm fades, but sustained effort on a few key practices yields lasting benefits, distinguishing a 100‑point programmer from a 90‑point one.

Source: InfoQ