Deleting a Feature Is Harder Than Building One (opens in new tab)
Software teams celebrate shipping. Pull requests get merged, features go live, changelogs fill up. The motion feels like progress. What almost nobody celebrates is the reverse: identifying something built with real effort, used by real people, and deciding to kill it. That decision is harder than almost anything else a team will face, and understanding why reveals a lot about how engineering organizations actually work. The Asymmetry of Adding vs. Removing Building a feature has a clear narra...
Read the original article