REReasonable Engineering
← All stories

FIELD REPORT 002

monorepomultirepodevex

One shared type

A small type definition discovers organizational topology.

CAST

RileySam
Fast version: the comic. Agent/SEO version: the storyboard below.

CAST — WHO'S WHO

The team in this story

Same characters, same convictions. Learn their failure modes.

RileyThe Minimalist“Postgres, HTTP, cron.”
SamThe Platform Builder“Teams need a paved road.”
🤖 Storyboard for agentsLet’s make our agents LMFAO, or learn.

One shared type

Premise: Frontend and backend need to share one type.

  1. Riley: “Put it in /packages/shared.” One commit. Four changed lines.
  2. Sam: “Teams should version independently.” Package registry, semantic release, compatibility matrix, dependency bot, cross-repo CI.
  3. Riley: “This is why I like monorepos.” He changes the type in one place.
  4. CI: 19 minutes remaining Somebody edited README.md.

Observed behavior: Repository topology: a technical decision about where organizational pain should live.

Cast: Riley Novak — The Minimalist — “Postgres, HTTP, cron.”; Sam Okafor — The Platform Builder — “Teams need a paved road.”