There are few places in a codebase where the time saved in "developer productivity" will be greater…

Often the justification for rewrites like this is “developer productivity.” As a believer in developer productivity, I think this is a fine motivation, but there need to be measures behind that intuition that you can point to. “We need to make it possible to ship the code base to production on demand” is a much more compelling and clear project than “we need to rewrite this system to increase developer productivity.” Identify the actual blockers to productivity that you are experiencing when working with this system, and make a plan to fix those.
Avoiding the Rewrite Trap
456
18
Camille Fournier
Justin James
·Follow
Jul 7, 2023
--
There are few places in a codebase where the time saved in "developer productivity" will be greater than the time to rewrite it... and typically that's true for a "refactor" as well.
While everyone likes a nicely refactored codebase, and it does improve developer productivity and happiness, the truth is, these activities rarely have actual, measurable ROI.
J.Ja
--
--
Written by Justin James523 Followers
·97 Following
OutSystems MVP & longtime technical writer
No responses yet
Help
Status
About
Careers
Press
Blog
Privacy
Terms
Text to speech
Teams