📎 Webclip
The traits of a proficient programmer
The article argues that competence is knowing how to get things done, while proficiency is knowing why a method fits a problem and how the parts connect to the whole. It uses programming examples to show that a proficient developer can judge when patterns help, when they break down, and when they should be set aside.
Reading notes#
- Competence means having enough experience and knowledge to get stuff done.
- Proficiency means knowing why something is done a certain way and how it fits into the big picture.
- A proficient practitioner is always competent, but a competent practitioner may not be proficient.
- The article uses the Dreyfus Model of Skill Acquisition as background for the path from beginner to expert.
- For programmers, competence includes revision control, coding style, continuous integration, databases, responsive layouts, and service APIs.
- The main bottleneck described is the move from competence to proficiency.
- The difference between beginner and expert is not only how much stuff you know.
- Proficiency is about understanding why you do things a certain way and how the parts fit into the whole.
- A competent programmer can learn a pattern like Memento and implement it, but may still apply it inappropriately.
- A proficient programmer can see when Memento breaks down, consider alternatives, and adapt the idea to the use case.
- A proficient programmer also knows when design patterns are not the right topic at all.
- The article describes proficiency as a holistic mindset.
- Patterns, principles, idioms, libraries, and language features are tools, and the right tool should fit the job.
- The article suggests explaining your reasoning in the context of the current problem instead of relying on generic best practices.
- It recommends learning fewer things better and applying them in different contexts.
- It recommends studying cases where rules are broken successfully.
- It recommends digging into primary sources rather than only reading summaries.
- It recommends entering unfamiliar projects and working without relying on memorized routines.
- It recommends asking others why they do things, while demanding examples and context.
- It recommends developing a small number of specific skills to an extreme level.
- The article closes by saying that proficiency can lead toward mastery.
