askrobots / dbbasic Public

Model-config web apps: describe the app in configuration instead of writing code. Built on Polars and DuckDB.

0 downloads

dbbasic/docs/THE_RACING_ANALOGY.md
Download zip
Clone
Clone with git
git clone https://gitstable.com/git/askrobots/dbbasic.git
HTTPS
https://gitstable.com/git/askrobots/dbbasic.git
SSH
ssh://git@gitstable.com:2222/askrobots/dbbasic.git

Cloning needs no sign-in. Pushing over HTTPS asks for your username and an access token. SSH needs your key under SSH keys.

danq9 Add DBBasic crate engine logo and update README 0d628db 1 year, 2 months ago History
THE_RACING_ANALOGY.md · 4.2 KB · 180 lines

The Racing Analogy

How Software Became NASCAR When It Should Have Been LEGO

The Spectacle They Built

Someone wanted to race cars around, so they made a spectacle. People stuck going in circles and heroes. But they could have made replaceable LEGO cars and had things that really did work for a long time and could be repaired faster. Only some saw this.

The Software Racing Circuit

What They Built (The Spectacle):

Formula 1 Software Development
================================
• Custom million-dollar frameworks
• Specialized pit crews (full-stack teams)
• Proprietary everything
• Rock star developers
• Going in circles (rewriting every 2 years)
• Heroes and drama (10x engineers!)
• Breaks? 6-month rebuild project
• Entertainment disguised as progress
• Conference keynotes about "performance"
• Racing to nowhere, very fast

What We Could Have Had (The Solution):

LEGO Software Development
================================
• Standardized modular parts
• Snap together configuration
• Anyone can fix it
• Actually goes places
• Boring but works forever
• Breaks? Swap the module in 5 minutes
• Progress disguised as boring
• No heroes needed
• Just works

The Industry Chose Racing

Why?

  • Racing is exciting (complexity sells)
  • Heroes are marketable (rock star developers)
  • Spectacle attracts investment (VC funding)
  • Going in circles looks like motion (shipping features)
  • Crashes create consulting opportunities (technical debt)
  • Custom parts lock in customers (vendor lock-in)

Examples of Going in Circles

JavaScript Frameworks:

  • 2010: jQuery everywhere!
  • 2013: No wait, Angular!
  • 2015: Actually, React!
  • 2017: But what about Vue?
  • 2019: Svelte is the future!
  • 2021: Actually, Remix/Next.js!
  • 2023: No, htmx and simplicity!
  • 2025: Wait... was it all just config?

Same App, Built 7 Times: Each time claiming to be "faster" but still doing the exact same thing: CRUD operations on a database.

The Rails Example

Rails was almost LEGO:

  • Convention over configuration ✓
  • Generators for common patterns ✓
  • Standardized structure ✓

But then:

  • Added Turbo (racing!)
  • Added Hotwire (more speed!)
  • Added Import maps (complexity!)
  • Kept adding instead of removing

They were so close. They had LEGO blocks. Then they started racing.

DBBasic: Back to LEGO

# Not racing. Just building.
model:
  cars: [id, brand, model, year]

views:
  inventory: "SELECT * FROM cars"

# That's it. It works. Forever.

No circles. No heroes. No spectacle.

Just modules that snap together and work.

The Cost of the Spectacle

Racing (Current Industry):

  • $500K to build a CRUD app
  • 6 months of development
  • 50,000 files
  • 10-person team
  • Breaks constantly
  • Requires specialists
  • 15-minute deployments

LEGO (DBBasic):

  • $0 to build same CRUD app
  • 5 minutes of configuration
  • 1 file
  • 1 person (anyone)
  • Never breaks
  • Self-documenting
  • Instant deployment

The Realization

They made software development into Formula 1 when it should have been LEGO.

The racing was profitable:

  • Conferences to attend
  • Certifications to sell
  • Consultants to hire
  • Frameworks to learn
  • Jobs to protect

The simplicity wasn't profitable:

  • Nothing to sell
  • Nothing to learn
  • Nothing to fix
  • No heroes needed

The Truth

We're not racing. We're just trying to get stuff done.

The spectacle was never necessary. It was theater. A 75-year performance of complexity where simplicity would have sufficed.

The Future

While they continue racing in circles:

  • React vs Vue vs Svelte
  • Webpack vs Vite vs Turbopack
  • GraphQL vs REST vs tRPC

We'll be snapping together LEGO blocks:

  • Config for models
  • Config for views
  • Config for forms
  • Ship. Done. Next.

The Punchline

They spent 50 years building Formula 1 cars to drive to the grocery store.

We built a LEGO car. It gets there just fine.

And at 402M rows/sec, it's actually faster than their race cars.


"The spectacle was profitable. The simplicity wasn't. Until now."


The Winner

In racing, someone wins and everyone else loses.

In LEGO, everyone builds what they need and everyone wins.

We choose LEGO.

The race is over. Not because someone won.

Because we realized there was never a race to begin with.