Andrey Markin
  • home
  • services
  • projects
  • blog
  • directory
    • Tool
    • Library
    • Repo
    • Article
    • XTweet
    • Guideline
    • Video
  • courses
  • resume
  • about
  • contact
  • meet

Mark Life Ltd

  1. Home
  2. Directory
  3. Rethink Everything
Meet

Mark Life Ltd

BG208147965

HomeContactPrivacyLLM-friendlyBlog RSSDirectory RSS
  1. Directory
  2. It's Time To Rethink Everything
VideoAI CodingInfrastructureagents

It's Time To Rethink Everything

Theo Browne's CascadiaJS 2026 talk arguing that AI is a "new cloud moment" — just as the cloud removed the cost of provisioning servers, agents remove the cost of building, so the sacred rules of software (file systems, codebases, packages, git, deployment) are worth tearing down and rebuilding from first principles.

Added June 18, 2026Theo Browne (@t3dotgg)
Visit video

Recorded live at CascadiaJS 2026 in Seattle.

The cloud changed software by removing the need to pre-acquire servers and predict scale — experimentation got cheap, and products like Slack or Salesforce became possible. Theo's argument: AI is the same kind of shift. You now get Amazon-scale software without Amazon-scale teams, which means the assumptions baked into how we build are worth re-examining.

Now is the time to try the thing that feels stupid because every preconceived notion we have doesn't matter anymore.

The sacred rules worth questioning

  • Git — why can't a public repo have private parts, team-only files, or a beta branch nobody else can see?
  • File systems — why can't a file live in two folders at once? Why does a compiler need read/write access to a real directory (and therefore a real kernel, isolate, Docker image)?
  • Codebases & packages — when an agent can rewrite a project in a week or reimplement a package from spec, the code itself stops mattering the way it used to.
  • Deployment — building dropped from ~40–100 hours to ~30 minutes, but deploying still takes hours (half of it in the Google OAuth consent screen). The build/deploy ratio no longer makes sense.

Breadth vs. depth

Software used to win by going deep on one vertical slice, because covering the full breadth meant missing features everyone needed. With agents on both sides, you can cover the breadth and let users prompt the depth — the special-snowflake features become their problem, not yours.

Lakebed

To prove the point, Theo demos Lakebed — npx lakebed new, npx lakebed deploy, and you get a live app with real sync and working auth across platforms, no dashboards or env vars. Building it meant rebuilding the CLI, a frontend framework, a backend framework, a bundler, a language runtime, and a compiler to run in isolates. It's "a shitty cloud for shitty apps" — not how you'd build the next Facebook, but proof we don't have to build the way we did before.

Chapters

  • 00:00 — Introduction: It's Time to Rethink Everything
  • 01:04 — How the Cloud Changed Software Forever
  • 03:22 — AI as the New Cloud Moment
  • 05:13 — Small Teams, Massive Leverage
  • 06:26 — Questioning Software's Sacred Rules
  • 07:27 — Why File Systems Might Be Wrong
  • 09:17 — Do Codebases and Packages Still Matter?
  • 10:30 — Rebuilding Software From First Principles
  • 14:54 — The Deployment Problem
  • 18:13 — Live Demo: Building Lakebed
  • 22:29 — Build Bigger

Related

  • EveOpen-source agent framework from Vercel — define agents as directories of TypeScript and Markdown config and deploy them as standard Vercel projects.
  • FlueTypeScript framework for building durable AI agents and workflows with no vendor lock-in — write once, deploy anywhere, run on any LLM.
  • teachMatt Pocock's skill that turns a coding agent into a personal tutor — it builds a stateful learning workspace and designs lessons within your zone of proximal development to teach you any skill or concept over multiple sessions.
  • fffThe fastest and most accurate file search toolkit for AI agents, Neovim, Rust, C, and Node. Keeps an in-memory index for sub-10ms queries instead of spawning ripgrep/fzf per search.