Introduction and Personal Anecdote
- The speaker, Dan Shipper, Co-founder & CEO of Every, introduces himself as the last speaker of the day.
- He expresses surprise at the audience size, jokingly referencing a tweet about AI FOMO in New York vs. San Francisco, affirming his love for New York.
The AI-Native Playbook is Being Invented
- Shipper states that there is no existing playbook for building AI-native companies, or if there is, he doesn't have it.
- He believes "What an AI-native company even is is being invented right now by all of us."
- His talk will offer "dispatches from the frontier" based on Every's experiences.
10x Difference with 100% AI Engineers
- He highlights a "10x difference between an org with 90% vs. 100% AI engineers."
- This is because with a traditional engineering method, even 10% non-AI work can pull the entire organization back.
About Every
- Every runs 6 business units and 4 software products with just 15 full-time employees.
- They've grown MRR double digits every month for the last 6 months, with 7,000+ paying subscribers.
- They've raised over $1M in total.
- "99% of our code is written by AI agents."
Single-Developer Apps
- Each of Every's apps is built and run by a single developer.
- He showcases "Cora," an AI email management app that summarizes emails and provides an assistant, primarily built by one engineer.
- He also shows "Monologue," a speech-to-text app, and "Spiral," a planning and writing app, both built by single engineers and complex.
- This level of output by single developers "would obviously not have been possible to do even a year ago."
Benefits of AI-Native Engineering
- Parallel Work: Developers can work on multiple features and bugs in parallel.
- Rapid Prototyping: Risky ideas can be rapidly prototyped, allowing for more experiments.
- Demo Culture: Companies move toward a demo culture instead of a written or oral culture, enabling weirder things that one can only get if they can "feel it."
Compounding Engineering Process
- AI has caused Every to create an entirely new set of engineering primitives and processes.
- This process is called "compounding engineering."
- Traditional engineering: each feature makes the next feature harder to build.
- Compounding engineering: each feature makes the next feature easier to build.
- It's a four-step loop:
- Plan: Detailed planning when working with AI agents is crucial.
- Delegate: Tell the AI agent to execute the plan.
- Assess: Evaluate whether the agent's work is good (tests, trial, agent code review, human code review).
- Codify: This is the "money step" where learned tacit knowledge is compounded back into explicit prompts for the organization to use.
Powerful Second-Order Effects
- Tacit Code-Sharing: Developers can learn from each other's code with no time cost, as AI can easily understand and translate across different tech stacks/languages.
- New Hires Productivity: New hires are productive on their first day because codified knowledge allows AI agents to set up environments and guide them effectively. This also enables hiring expert freelancers to "drop in" for specific tasks.
- Flexible Tech Stack: Teams can work with the stack and language they like best; AI translates between them, removing the need for standardization.
- Managers Commit Code: Managers, if technical, can commit code (even the CEO) because AI allows for working with "fractured attention," making it possible to contribute to the codebase without deep immersion.
Summary of Key Points
- 10x difference when you hit 100% AI adoption.
- A single engineer should be able to build and maintain a complex, production product.
- Compounding engineering makes each feature easier to build.
- There are many non-obvious second-order effects once you adopt it.
- Many people in SF don't know this yet. (A humorous jab at Silicon Valley).
Every - The Edge of AI
- Every provides ideas, apps, and training to help people stay at the edge of AI.
- They offer a daily AI newsletter, reviews of new models and products, a bundle of AI apps, and consulting for large companies.