Thought Leaders

James Phoenix
James Phoenix

People to follow for compound engineering, context engineering, and AI agent development.


Compound Engineering & AI Agents

Vinci Rufus

Website: vincirufus.com

Focus Areas:

  • Agentic AI systems and multi-agent architectures
  • Compound engineering methodologies
  • AI agent design patterns and reliability
  • Context engineering and prompt optimization
  • Production-ready AI deployment

Key Articles:

Philosophy: “Believes in Agentic AI” – focuses on building swarms of intelligent agents

Notable themes: Business-to-Agent (B2A) SaaS, the evolution of software economics through AI, the distinction between demo agents and production systems, Model Context Protocol standardization.

Presence: Active on GitHub and LinkedIn with 40+ technical articles

Why Follow: Practical implementation focus over theory. Addresses real challenges like reliability, evaluation systems, and the transition from conversational to truly agentic interfaces.


Dex Horthy (HumanLayer)

Website: humanlayer.dev

Focus Areas:

  • Human-in-the-loop agent design
  • Production agent architecture
  • Agent approval workflows

Key Work:

Why Follow: Deep practical knowledge of agent deployment challenges and human-AI collaboration patterns.


Geoffrey Huntley

Focus Areas:

  • RALPH Loop methodology originator
  • Agent orchestration patterns
  • Developer tooling

Why Follow: Original creator of the RALPH Loop concept that enables fresh-context agent iteration.

Leanpub Book

Read The Meta-Engineer

A practical book on building autonomous AI systems with Claude Code, context engineering, verification loops, and production harnesses.

Continuously updated
Claude Code + agentic systems
View Book

Steve Yegge

Focus Areas:

  • “Gas Town” multi-agent future concept
  • Software engineering evolution
  • Developer experience

Why Follow: Thought leader on how multi-agent systems will reshape software development.


Will Larson (Lethain)

Website: lethain.com

Focus Areas:

  • Engineering leadership and management
  • Infrastructure at scale
  • Systems thinking

Key Work:

Why Follow: Brings engineering leadership perspective to compound engineering. His analysis emphasizes that “the quality of your codebase, tests, and continuous integration harness” matters more than the agent itself.


Anthropic Engineering Team

Website: anthropic.com/engineering

Focus Areas:

  • AI safety and alignment
  • Claude capabilities and best practices
  • Production AI deployment patterns

Key Work:

Why Follow: First-party guidance on building robust agent systems with Claude.


How to Use This List

  1. Subscribe to RSS/newsletters – Stay current on new articles
  2. Read foundational pieces – Articles linked above are canonical
  3. Cross-reference with knowledge base – See how concepts connect to your own documentation
  4. Track emerging patterns – New methodologies often appear here first

Adding to This List

When adding new thought leaders:

### [Name]

**Website:** [url]

**Focus Areas:**
- Area 1
- Area 2

**Key Work:**
- [Article Title](url) - Brief description

**Why Follow:** One sentence on their unique value.

Related

Topics
Agent ArchitectureAi AgentsContext EngineeringMeta DevelopmentPrompt Engineering

Newsletter

Become a better AI engineer

Weekly deep dives on production AI systems, context engineering, and the patterns that compound. No fluff, no tutorials. Just what works.

Join 306K+ developers. No spam. Unsubscribe anytime.


More Insights

Cover Image for Computer Use Kills the Config Tax, Not the Trust Tax

Computer Use Kills the Config Tax, Not the Trust Tax

My sister hates job applications because they make her re-submit information she already has. That is the same pain as API app review, and the same agent that lives in my codebase can dissolve both. This feels insane, and it is the new default shape of the work.

James Phoenix
James Phoenix
Cover Image for Sentry Errors Should Spawn Agents on Your Own Machine

Sentry Errors Should Spawn Agents on Your Own Machine

A new production error is an event. Events should trigger work, not sit in a dashboard. So I wired Sentry to spawn a coding agent on my own hardware, point it at my exact stack, and open a draft PR with a fix.

James Phoenix
James Phoenix