liveBook · Manning

Era

As explained in Crack Any Codebase with AI

An era is a defined historical period characterized by a distinct strategy, product identity, or pattern of activity.

An era is a named period in a product’s history defined by the team’s dominant strategy, product identity, and turning point. It converts a flat commit log into a narrative about changing bets. section 6.3

Build eras from three compressed signals:

  • Directory activity: active date ranges and peak months reveal where attention concentrated. section 6.3
  • Directory lifecycles: appearing, disappearing, or going quiet exposes structural transitions. section 6.3
  • Large additions and deletions identify concrete commits that opened or closed an era. section 6.3

A product-history timeline

A Ghost history can be read as four eras: “The WordPress Killer,” “The Platform That Wasn’t,” “The Membership Pivot,” and “The Creator Platform.” Each names a strategic bet rather than a directory change. section 6.3

Name each era after the bet the team was making, then explain the turning point that ended it and became the next era’s origin story. section 6.3

How Crack Any Codebase with AI covers it

How deep it goes
Combines directory activity, lifecycle changes, and bulk commits, then stops at strategic interpretation rather than exhaustive changelog detail.
Examples
Uses Ghost’s four named eras and directory transitions such as core going quiet while apps appears.
What it assumes
Requires compressed commit activity, directory pivots, and notable additions or deletions rather than an unfiltered commit log.
What you can do after
Evaluate product direction by dividing commit history into three to five named eras with identities, bets, and endings.
How it connects
Connects Git history with product strategy, directory lifecycles, pivots, and turning points.

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.