What is mattwood.fyi?

A live, structured feed of riffs and links from Matt Wood, Chief AI & Technology Officer at AWS — readable by people and queryable by agents as a typed knowledge graph.

Is there an API and is it free?

Yes. A public, read-only query API is available with no authentication and no API keys. See https://mattwood.fyi/openapi.json and https://mattwood.fyi/docs.

How should an AI agent use this site?

Fetch https://mattwood.fyi/feed.json for the full structured feed, or query the API for keyword/semantic search and the connection graph. See https://mattwood.fyi/agents/ for when-to-use guidance.

Lessons I've Learned at Warp Building for Developers

Connections

Develops into

The Agent Stack Bet - by Addy Osmani - Elevate The three-phase model of AI coding (autocomplete, chat, agents) sets up the 'agent stack' framing that Osmani builds on as the next evolutionary stage.
Loop Engineering - by Addy Osmani - Elevate Warp's description of agentic coding as the emerging third phase leads directly into loop engineering as the practice for designing agent-driving systems.

Supported by

ChatGPT Desktop App for Linux Now in Preview ChatGPT's Linux desktop app with Codex integration directly addresses the developer workflow lessons discussed at Warp — bringing AI assistance natively into the terminal/IDE environment rather than requiring context-switching to a browser
Saggar: Terminal Session Manager for Mac Saggar's session/task status management directly addresses the developer experience lessons described in building Warp — organizing terminal sessions around project state is a core developer productivity problem
Secrets Don't Belong in Config Lessons building developer tooling at Warp align with the article's thesis: developer experience improves when secrets management is a first-class concern separated from general configuration rather than bolted on
Omarchy: Modern Linux Distribution Both reflect lessons from building developer-focused tools with strong opinions — Omarchy's opinionated approach mirrors Warp's philosophy of making deliberate UX tradeoffs to serve developer workflows better
How I Over-Engineered My Book Both derive lessons from first-hand building experience; the over-engineering post's cautionary reflection on excessive complexity aligns with lessons-learned narratives about pragmatic developer decisions

8 Myths of Software Development with AI ACM Queue practitioner-focused systems articles share the same audience and knowledge domain as lessons learned building developer tools at companies like Warp
8 Myths of Software Development with AI ACM Queue practical systems articles and lessons from building developer tools like Warp share the same practitioner-audience focus on real-world software engineering insights
Herdr is joining Y Combinator. The runtime stays open. Both focus on developer tooling in terminal/CLI environments, with Warp's lessons about building for developers directly applicable to Herdr's growth trajectory
Forking dotenvy into dotenv-ng Both address developer tooling reliability: dotenv-ng fixes a silent correctness bug that wastes developer time debugging authentication failures, echoing the developer experience lessons from building Warp
TerminalWidget for Mac, iPhone, and iPad Both address developer tooling experience; TerminalWidget and Warp's lessons both focus on making terminal/developer workflows more accessible and integrated into modern interfaces

Type:	link
First published:	Thursday, 4 June 2026 at 12:00 UTC
Location:	https://www.linkedin.com/pulse/lessons-ive-learned-warp-building-developers-zach-lloyd-cbgoc
URL:	https://mattwood.fyi/i/8691c6a4

I'm Matt Wood, and this is For Your Information. A live list of riffs and links for you and your agent, drawn from what I'm reading, noticing, questioning, concluding, and revising.

Connections