liveBook · Manning

Feature deletion

As explained in Crack Any Codebase with AI

Feature deletion is the removal of a previously implemented product capability from a software system.

Feature deletion removes a previously implemented capability and records a product decision: what a team sacrifices can matter as much as what it ships. section 6.5

Investigate a deleted feature as a graveyard entry:

  • Find commits deleting five or more files from one folder; bulk deletion often signals a removed feature rather than routine cleanup. section 6.5
  • Inspect the complete git show diff, including deleted source code, instead of inferring behavior from file names. section 6.5
  • Describe the user-facing behavior, then record the commit hash, subject, author, date, and product era. section 6.5

Read the code, not the folder name

A deleted loyalty/ directory might suggest a finished rewards program, but its diff may reveal only an unwired stub. In Ghost's membership pivot, removing the original plugin system and subscribers v1 made room for members, Stripe, and the Portal UI. section 6.5

Figure 6.7 A project advertises what shipped, but its git history also records what was killed. These deletions (a plugin system that never found an audience, an AMP integration Google abandoned, a replaced subscribers v1) show which bets the team walked away from.

Use the figure to compare shipped additions with the plugin system, AMP integration, and subscribers v1 that teams abandoned. section 6.5

How Crack Any Codebase with AI covers it

How deep it goes
Provides a discovery heuristic, full-diff investigation method, and graveyard-entry format, but does not explain implementation mechanics.
Examples
Uses Ghost's plugin system and subscribers v1, an abandoned AMP integration, and a hypothetical loyalty directory as investigative examples.
What it assumes
Assumes access to repository history and Git diffs while teaching readers to distinguish paths from actual feature behavior.
What you can do after
Diagnose removed capabilities by locating bulk deletions, reading full diffs, and writing dated product-focused graveyard entries.
How it connects
Connects feature deletion to Git history and product strategy through the relationship between shipped additions and abandoned bets.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Crack Any Codebase with AI. The section links point to the parts of the book it draws on.