Guidelines for Becoming a 100‑Point Programmer: Saying Yes/No, Building Knowledge, and Good Practices

Be Cautious About Saying Yes

Before committing to a task, a top‑performing programmer should fully understand the development requirements, workload, and team expectations; otherwise, over‑promising can lead to missed deadlines or unmet expectations, eroding trust over time. It is advisable to ask many "why" questions, clarify the work with colleagues and leaders, and only then agree.

Dare to Say No

When faced with clearly unreasonable requests, one should consider refusing, provided there are well‑prepared, comprehensive reasons. Saying no should be infrequent but decisive; a high‑performing programmer knows their role, distinguishes reasonable from unreasonable demands, and communicates with leadership to gain support.

Build Your Own Knowledge System

In an era of information overload, fragmented knowledge is abundant, and systematic learning time is scarce. Without a personal knowledge framework, one can be overwhelmed. It is recommended to use a wiki or other knowledge‑management tools to categorize topics such as soft skills, architecture, languages, front‑end, back‑end, etc., and regularly consolidate insights, allowing the brain to retain only the framework, major categories, and key points.

Cultivate a Big‑Picture Perspective

Programmers often focus narrowly on their own tasks, ignoring team progress, overall system architecture, and other modules. Over time this limits growth, especially in large companies where one may become a mere cog. By observing what others are doing, understanding team plans, and reviewing system documentation, a programmer gains deeper insight into product design and leadership decisions, which benefits their career.

Code Standards

Early‑career developers should adopt good coding standards, starting with the company’s existing guidelines (or creating them if none exist). From variable naming to module division, some rules can be enforced by tooling, while others require personal discipline. The classic reference is "Code Complete"; establishing a consistent coding style is a fundamental step.

Code Review

Code review is crucial for programmer growth. Even if a company does not formalize the process, developers should encourage peers to review their code and review others’ code to gain feedback, learn new approaches, and foster a collaborative habit.

Learn Business Knowledge

A top‑performing programmer should also understand business domain knowledge. Knowing the business context helps clarify vague requirements, enables better communication with product teams, and leads to superior design and architecture, enhancing the programmer’s standing within the team.

Persistence

Developing good habits requires persistence; theory without practice is ineffective. Consistently applying a few key recommendations yields substantial benefits, making the "100‑point programmer" distinguished not by raw intelligence but by the breadth of good habits.

In short, the difference between a 100‑point and a 90‑point programmer lies not in the scoring system but in the consistent application of disciplined practices.