Developer Usefulness
Becoming a useful developer requires more than simply being a developer. Usefulness requires scheduling and protecting leverage-creating work. Developer usefulness depends on whether leverage work is deliberately scheduled rather than surr…
2 sources - 7 claims
Becoming a useful developer requires more than simply being a developer. Usefulness requires scheduling and protecting leverage-creating work. Developer usefulness depends on whether leverage work is deliberately scheduled rather than surrendered to calendar invites. A developer can be operationally critical while remaining invisible in planning and blocked from leadership. The article identifies reactive firefighting as a central career risk for developers.