≡endo/⎇ main /why.md
endo/why.md

# Why Endo

> Endo is an experiment for the balanced: the people who believe AI is a game changer but know that to do game-changing things with it, they cannot outsource their understanding.

The UX of most new agentic development environments encourages offloading your thinking to Opus (they have to; it means more profit), and that's not a bad thing: Opus can go from a single prompt to production. But you're not achieving any form of domain expertise without exercising the LLM in your head, and that's what the IDE was for. It was never just a place to write code; it was your gym, where you could read code, inspect memory, read PDFs, write a blog post. There's no reason the equipment in that gym can't be replaced with AI-powered versions: highlight the part of the Raft paper you don't get and ask Opus to explain it, or stop at a breakpoint and ask Opus why your struct with a u64 and a u8 takes 16 bytes instead of 9.

So Endo starts with a traditional IDE and sees how far we can push it toward the extreme without sacrificing the benefits the traditional IDE gave us: a place to practice, to learn, to attain domain expertise.

- If the day calls for full vibe coding, no problem, Endo's got you.

- If it calls for digging in, sweating and pushing the LLM in your head, Endo's got you too, and you won't be alone: Opus is a great workout partner.

// see this post by Andrej Karpathy

// next: idea.md

-- NORMAL --  1:1 14 linesMarkdownUTF-8