The process of building systems with software and writing code is a complex undertaking. Although there are many ways to categorize programmers, one foundational way is by how they think about and organize their work. This article explores three distinct types of programmers: the coder, the software developer, and the software engineer.
Defining the Three Types
The three types are not strictly about levels of experience, though experience may play a part. These categories represent distinct groups that behave differently and achieve different results. While a programmer may take on each of these roles at different times, these differences are often driven by the environments in which they work.
This concept can be related to Kent Beck's idea of the forest and the desert, where strategies that are necessary for survival in harsh conditions may seem unnecessary in more favorable environments. Recognizing the current environment helps programmers determine if change is needed and worth the effort.
The Coder
Coders primarily translate detailed instructions into code. They often view their core skill as proficiency in a programming language. They may see understanding the underlying problem as less important than the act of writing the code itself.
-
Characteristics:
-
Focus on translating specifications into code.
-
May resist testing their own code.
-
May exhibit learned helplessness due to organizational constraints.
-
-
Challenges:
-
Can be victims of dysfunctional organizational structures.
-
May use external control as an excuse to avoid certain tasks.
-
Often produce systems that are not user-friendly or maintainable.
-
Coders in restrictive environments may be told to remove bug fixes that aren't in the plan or need to jump through bureaucratic hoops to add a new class. This highlights how organizational culture can force programmers into the coder role. When programmers say "It's not my fault, someone else didn't get the requirements right," they are likely thinking and working as a coder.
The Software Developer
Software developers take more personal responsibility for their work. They see their job as solving problems for users using software. This includes the design of the system.
-
Characteristics:
-
Solve problems using software tools.
-
Responsible for the design of the system.
-
Take ownership and correct issues as needed.
-
-
Benefits:
-
Leads to better systems compared to systems built by coders.
-
More effective than simple translation of solutions into code.
-
Freedom and ownership are strong predictors of high-performing teams.
-
This is a stark contrast to the coder role. Software developers have the freedom to change things in unpredictable ways when they hit unforeseen problems. It is more effective than the coder role.
The Problem with Tailorism:
Organizations that treat software development as a simple translation of specifications into code often fall into the trap of tailorism. This approach, which decomposes work into specialized tasks, may seem efficient but can stifle creativity and adaptability. It restricts the freedom of individuals to make necessary design changes, ultimately hindering overall performance.
With the rise of AI programming, the role of software developers is becoming even more crucial. AI can translate instructions into code but lack the insight to understand the problem and design creative solutions.
Advice for Coders:
If you recognize yourself as a coder, it is advised to better understand the problems you work on. Develop skills to adopt a more organized approach to problem-solving. Improve your critical thinking of design choices. Learn TDD, BDD, CI, and CD. Learn to see your work more from the perspective of a user.
The Software Engineer
Software engineers apply a scientifically rational approach to problem-solving. They are able to determine the releaseability of their system after every small change.
-
Characteristics:
-
Employ a scientific and rational approach.
-
Prioritize continuous delivery.
-
Can determine the releaseability of their system at any point.
-
-
Benefits:
-
Produce better software faster.
-
Create more enjoyable work environments.
-
Contribute to more profitable companies.
-
The principles of rational problem-solving are key to doing well. When solving complex problems, adopt a problem-solving approach and get good at it.
Conclusion
These categories may be subjective, but can be useful in determining where teams are in the journey towards excellence. While many are challenged on software not being engineering, most software development isn't practiced as engineering. There are many more coders and software developers. There is no argument that building teams of coders is better than building teams of developers. Decomposing software development into coding tasks is an exercise in futility.