Platform

Definition

Platform coverage in this archive spans 3 posts from Dec 2017 to Mar 2026 and deals with structural tradeoffs: coupling, failure boundaries, and long-term change cost. The strongest adjacent threads are devops, engineering, and agenticops. Recurring title motifs include ai, platform, agent, and operations.

What the archive argues

• Most pieces recommend choosing the simplest architecture that can be operated confidently.
• The consistent theme from 2017 to 2026 is disciplined execution over hype cycles.
• This topic repeatedly intersects with devops, engineering, and agenticops, so design choices here rarely stand alone.

Execution checklist

• Define failure domains and data boundaries before introducing additional services or protocols.
• Start with the newest post to calibrate current constraints, then backtrack to older entries for first principles.
• When boundary questions appear, cross-read devops and engineering before committing implementation details.

Common failure modes

• Breaking systems into many parts without clear ownership of cross-service behavior.
• Choosing architecture for trend alignment rather than workload constraints.
• Applying guidance from 2017 to 2026 without revisiting assumptions as context changed.

Suggested reading path

• Start here (current state): AI Agent Operations and the Networking Bottleneck: Why AI Agents Fail on Legacy Infrastructure
• Then read (operating middle): Your Internal Platform Is Probably a Liability
• Finish with (foundational context): What I Learned Building Our Platform Team This Year

Related posts

• AI Agent Operations and the Networking Bottleneck: Why AI Agents Fail on Legacy Infrastructure
• Your Internal Platform Is Probably a Liability
• What I Learned Building Our Platform Team This Year

References

• The Twelve-Factor App
• Google SRE Book
• RFC 9110: HTTP Semantics