pavel

new model for engineering team structure in 2026: 2 people only one pirate and one architect the pirate's job is to move as fast as possible to develop valuable, shipped product features by vibe coding. the architect's job is to turn the product surface discovered by the pirate into a reliable, structured machine—also by vibe coding, but at a slower, more well-reasoned pace. every product needs a pirate but most product's only need an architect once they some form of PMF, and in that case they usually don't need one full-time. architects can work across many codebases and solve interesting technical challenges. pirates go hard on a product that they own end-to-end.

Claude Code on desktop can now preview your running apps, review your code, and handle CI failures and PRs in the background. Here’s what's new:

I have been at 100% AI-contributed code for a few months now. Here are 9 ways it's changed my brain: 1. WAY more time thinking about integration testing 2. Friction via pre-commit hooks/CI/strong types is now super desirable 3. AI has no taste for UI, prototype extremely aggressively before committing to a PRD 4. AI has no taste for software architecture, be extremely explicit about the modules you want and think about their interfaces 5. Deep, grey-box modules with simple interfaces are the KING - let AI control what's in the box to decrease your cognitive load 6. Huge reliance on Effect.ts for dependency injection and strongly typed errors 7. Much more meta-programming, turning my skills into repeatable SOP's 8. First I thought MOAR DOCS = BETTER but 'doc rot' is real. Better to just let the AI generate JIT docs during plan mode. 9. Much higher cognitive load to keep up with the changes the LLM makes to the codebase

Thinking of unshipping it due to many reports of having a large negative performance impact (clangd & rust-analyzer love using 40 GB of ram) I don’t use this feature myself because claude can just run the build to know