Profile 6 min read

Lessons from Charlie Sutton

Charlie Sutton, Atlassian’s Chief Design Officer after design leadership at Apple, Meta, and Nokia, has followed interaction design from mobile hardware to spatial computing and AI agents. His guiding principle is simple: calm is smooth; smooth is fast.
Profile 7 min read

Lessons from Chung Ju-Yung

Chung Ju-yung escaped his family’s farm and founded Hyundai Group, applying a philosophy of immediate physical action. Entering shipbuilding without a shipyard or capital, he exemplified the manual stubbornness behind South Korea’s post-war industrial scale.
Profile 8 min read

Lessons from Lilian Weng

Lilian Weng, former OpenAI VP of Research and Safety and author of Lil’Log, makes frontier AI legible. Her work traces reinforcement learning and robotics toward safe, agentic language models, asking how capable systems can remain aligned and human-centric.
Digest 6 min read

Daily Digest - 2026-05-20

Companies gain leverage by embedding agents across operations, but lasting enterprise value requires model-agnostic architecture, redesigned workflows, and deployment discipline rather than vendor lock-in or superficial AI wrappers.
Profile 10 min read

Lessons from Eben Upton

Eben Upton, computer scientist and Raspberry Pi co-founder, designed an affordable microcomputer that revitalized computer science education and became an industrial standard. His approach joins hardware architecture, cost-engineering, and a licence to tinker with owned tools.
1 min read

GTM Engineering — Series Index

GTM engineering turns revenue operations from loosely configured tools into an explicit, testable system, progressing from data models and signal contracts through routing, reliability, experimentation, agent controls, observability, and audit.
3 min read

GTM Engineering Series #10: The GTM Engineering Audit

A GTM engineering audit should test explicit system behavior rather than inventory tools, examining object models, signal contracts, routing, operator surfaces, automation controls, ownership, and visible failure paths to expose operational fragility.
3 min read

GTM Engineering Series #9: GTM Observability

GTM observability must explain workflow behavior, not merely report outcomes, pairing latency, freshness, routing, quality, and agent traces with clear ownership so teams can detect, understand, and repair revenue-system failures.

Choose your reading rhythm.

Start with a weekly briefing, add daily notes, or hear only when a durable essay or research update is ready.
You've successfully subscribed to Antoine Buteau
You've successfully subscribed to Antoine Buteau
Welcome back! You've successfully signed in.
Press ESC to close.