📎 Webclip
Great Developers Don’t Just Write Great Code
The article defines a good developer by more than the ability to write code that works. Good code has good design, and good design is understandable for the next person who has to read it. That next person can be the original author, but the article stresses that developers often spend more time reading code than writing it.
Reading notes#
- Good developers need to write code that works and is designed so another developer can understand it.
- The article treats “Bill” as the person who later has to read, debug, review, document, or extend the code.
- Developers often spend more time reading code than writing it, so they also need skill in working with existing code.
- Legacy code is presented as a normal part of software work, not an exception.
- When reading an unfamiliar function or method, starting from the end can help reveal its purpose faster.
- If code is hard to understand, the article advises focusing on the code itself and not on blaming the author unless the goal is to improve the code or your own skills.
- Knowledge of the codebase matters for efficiency, and writing documentation about a region of code can help direct investigation and reveal missing questions.
- Even if developers mostly work with existing code, writing good new code still matters because other developers will have to use it.
