Becoming a Professional Software Developer: Identity Over Skills

Bart Wullems, writing from his experience as a software architect, describes a pattern he keeps seeing in which teams commit to unit testing, refactoring, and clean code at the start of a project, then abandon those practices as deadlines close in. He diagnoses an identity problem. Developers already know the practices; they just don’t see themselves as the kind of developer who follows them under pressure.

He borrows James Clear’s framing from Atomic Habits, arguing that lasting change comes from shifting identity. For a developer, that means moving from “I need to write unit tests” to “I am the kind of developer who always writes unit tests.”

Fichamento

#

• The gap between knowing best practices and following them under deadline pressure is framed as an identity problem.
• Small, consistent actions (writing code daily, even for five minutes, reading documentation, contributing to open source) work as reinforcement, each one framed as a vote for the identity the developer wants to hold.
• Clear’s advice to build systems rather than chase goals translates to daily habits over targets, a fixed daily practice block instead of “learn Python in three months.”
• Once the identity is established, growth opportunities are described as following naturally from habits already in place, without needing to force discipline.
• Wullems connects this to the “Hungry, Humble, Smart” framing from The Table Group’s Ideal Team Player model, treating it as evidence that identity-driven behavior extends to how people show up on a team, not just individual technical practice.