// Topics / Year Review

Year Review

Definition

Year Review coverage in this archive spans 3 posts from Dec 2016 to Dec 2023 and links technical decisions to margin, distribution, and execution durability. The strongest adjacent threads are ai, reflection, and personal. Recurring title motifs include stopped, everything, changed, and barely.

Working claims

  • The posts consistently push for explicit unit economics and practical tradeoffs over narrative hype.
  • The consistent theme from 2016 to 2023 is disciplined execution over hype cycles.
  • This topic repeatedly intersects with ai, reflection, and personal, so design choices here rarely stand alone.

How to apply this

  • Tie roadmap bets to measurable outcomes: cost, throughput, risk reduction, or revenue impact.
  • Start with the newest post to calibrate current constraints, then backtrack to older entries for first principles.
  • When boundary questions appear, cross-read ai and reflection before committing implementation details.

Where teams get burned

  • Treating technical strategy as branding instead of an operating constraint.
  • Running broad experiments without clear stop conditions or budget discipline.
  • Applying guidance from 2016 to 2023 without revisiting assumptions as context changed.

Suggested reading path

References

    2023: The Year Everything Changed (and I Barely Kept Up) A personal look back at 2023 -- watching AI reshape the industry in real time, and figuring out what matters next. year-review ai personal 2022: The Year the Music Stopped A personal look back at 2022: building through the downturn, watching ChatGPT arrive, and what the year taught me about building things that last. year-review reflection ai 2016: The Year I Stopped Fighting Infrastructure A personal look back at what mattered in 2016 -- Docker going mainstream, Kubernetes momentum, Go adoption, and lessons from building at Dropbyke and a fintech startup. year-review technology engineering