Think wider

Theo refines “bigger” into “wider” and distinguishes the range a product covers from the feature count in one area. 13:07 13:23.

He says an extensible architecture can let users build features within a product area that the product author did not predict. 14:37.

See AI Engineer World’s Fair 20267 and Theo Browne6.

Sources

  1. Everything we knew about software has changed — Theo Browne, @t3dotgg ​ - YouTube. Theo Browne. Breadth argument; used to distinguish range from depth. Accessed 2026-10-01.
  2. Everything we knew about software has changed — Theo Browne, @t3dotgg ​ - YouTube. Theo Browne. Extensibility argument; used for user-built vertical features. Accessed 2026-10-01.

Last changed 2026-10-07 in f1a00f2. Source on GitHub. Change log.

Linked from

  1. Agent guide. An Effect stack so pure (aspirational) Kit Langton will blush.

    Think wider — Theo Browne asks developers to cover more product breadth instead of adding depth in one narrow area.

  2. Change log. What changed in the files served here, newest first.

    Think wider — edited: feat(learn): teach cards 63 to 82 with plain lines, diagrams and snippets

  3. Full agent guide. An Effect stack so pure (aspirational) Kit Langton will blush.
  4. Purpose and boundaries of rat-stack (VISION.md). What this starter is for and what a useful copy should keep.

    ” A month later he refined it: “bigger is probably the wrong word… It’s time to think wider.” He means range, how much ground your software covers.

  5. Rat Stack lore | rat-stack. Short, source-grounded notes on the ideas and decisions behind rat-stack.

    Think wider — Theo Browne asks developers to cover more product breadth instead of adding depth in one narrow area.

  6. Source change history (log.md). The generated change log as Markdown.

    Think wider — edited: feat(learn): teach cards 63 to 82 with plain lines, diagrams and snippets

  7. Theo Browne. Theo Browne discusses broader software work and model reliability in public talks.

    Theo distinguishes product breadth from feature depth and describes how extension points, interfaces for adding features, let users build missing features.