📎 Webclip
Losing a dev means losing a treasure
The article says a good programmer becomes a treasure for a company because technical skill, experience, and problem-solving can decide whether a project succeeds or fails. It describes a career path that moves from onboarding to practical work, then maturity, then a settling phase where motivation can decline and the person starts questioning the job, the project, and the company.
It also says this loss is often underestimated, especially in small teams or poorly documented projects where knowledge is concentrated in a few people. To reduce turnover, companies should give programmers autonomy, adequate tools, access to training and documentation, and a real role in strategic and architectural decisions.
Reading notes#
- A programmer accumulates experience and skills inside the company over time, so leaving means losing more than a resource.
- The career path described in the article includes onboarding, first tasks, professional maturity, and a settling phase.
- In the settling phase, motivation can weaken and the programmer may question the current job, the project, and the company.
- Some programmers respond by improving code, structure, processes, and documentation.
- Others become discouraged, bored, and frustrated, then look for new projects or a new company.
- Losing a programmer can be especially serious in small teams and in projects with weak documentation and overlapping work.
- Replacing a departing programmer exactly is often unrealistic because each one has a distinct style, habits, and skills.
- A company should not expect a new hire to cover the predecessor’s work fully from day one.
- Retention depends on autonomy in daily work, with room to organize time and choose how to reach goals.
- The company should provide hardware, software, training resources, documentation, and technical support.
- The article also says programmers should feel part of the project through involvement in decisions, architecture, and planning.
- When those conditions exist, the programmer is less likely to look elsewhere and more likely to contribute to the team’s growth.
