Skip to content

Uncle J's Insider

Uncle J's Insider

Reading paths, organized by question: AI Organization OS, AI HR, Agentic Engineering, and real products.

Latest post May 8, 2026RSS

All posts

  1. From HR to AI: What 18 Years of Managing People Taught Me About Managing AgentsI spent 18 years in HR — layoffs at AB InBev, building people infrastructure at SnowPlus, leading 150 at Longfor. Then I left and started writing code. Four days, 52 spec documents, 105,000 lines. People asked what made me think I could do this. They were asking the wrong question. Managing fifty AI Agents and managing fifty people are the same job.
  2. Most "AI Agents" Are Just Chat Boxes in a CostumeEveryone is building "AI agents." Almost none of them are. After studying the Claude Code source leak, shipping my own agent SDK, and watching a founder show me a chat box and call it an autonomous system — here's what actually separates an agent from an LLM wrapper. Seven decisions. Seven rungs. One framework you can use in the next five minutes.
  3. Organization Design Is Agentic EngineeringI can't write a single line of code. 4 days. 52 modules. 2,716 tests passing. 105,000 lines of code. How? I spent 18 years learning to design systems that run without me watching. That system used to be called an organization. Now it's called an Agent team.
  4. From a Meeting Recording to a Running Project — In One AfternoonI went from a 90-minute meeting to a fully delivered project in 4 days — 52 dev specs, 2,716 tests passing, 105,000 lines of code, and a 24KB project constitution. No team. No Jira. Just one person, one terminal, and a swarm of AI agents. This is what agentic engineering actually looks like.
AI Engineering | Uncle J's Insider