Model-config web apps: describe the app in configuration instead of writing code. Built on Polars and DuckDB.
THE_NEW_DEVELOPMENT_LIFECYCLE.md · 5.1 KB · 243 lines
The New Development Lifecycle
How Software Development Actually Works Now
The Old Way (2000-2025)
User Request
↓ (days)
Product Manager writes User Stories
↓ (days)
Sprint Planning & Estimation
↓ (days)
Developer writes Code
↓ (hours)
Code Review
↓ (hours)
QA Testing
↓ (hours)
Deployment Pipeline
↓ (15+ minutes)
Production
↓
Bug Found → Start Over
Total: 2-4 weeks per feature
The DBBasic Way (2025+)
User Request
↓ (minutes)
PM writes Specification
↓ (seconds)
AI generates Config Change
↓ (instant)
Git Commit (version controlled)
↓ (3 seconds)
Automatic Validation
↓ (instant)
System Updates Itself
Total: 30 minutes per feature
Visual Process Flow
graph LR
User[User Request] --> PM[PM Specification]
PM --> Config[Config Change]
Config --> Git[Git Commit]
Git --> Auto[Auto Deploy]
Auto --> Live[Live System]
Live -.->|Instant Rollback| Git
style User fill:#e1f5fe
style PM fill:#fff3e0
style Config fill:#f3e5f5
style Git fill:#e8f5e9
style Auto fill:#fff9c4
style Live fill:#c8e6c9
The Three Layers
Layer 1: Requirements (Why)
requirement: "Users need to filter orders by date"
reason: "Too many orders to scroll through"
success: "Find orders quickly"
Layer 2: Specification (What)
specification:
feature: date_filter
interface:
type: date_range_picker
default: last_30_days
format: MM/DD/YYYY
behavior:
on_change: refresh_results
validation: end_date >= start_date
Layer 3: Config (How)
pages:
/orders:
filters:
date_range:
type: date_picker
query: "WHERE date BETWEEN ? AND ?"
Real Example: Adding User Avatars
Traditional Process (2 weeks)
- Day 1-2: User story writing & grooming
- Day 3: Sprint planning (4 story points)
- Day 4-8: Development
- Update database schema
- Write upload controller
- Add image processing
- Update user model
- Modify all views
- Write tests
- Day 9: Code review & fixes
- Day 10: QA testing
- Day 11: Bug fixes
- Day 12: Deployment to staging
- Day 13: Final testing
- Day 14: Production deployment
Lines of code changed: 500+ across 20 files
DBBasic Process (30 minutes)
- Minute 1-5: PM writes specification
feature: user_avatars
specification:
storage: cloud
formats: [jpg, png]
max_size: 5MB
display: circle_crop
- Minute 6-10: AI generates config changes
data:
users: +avatar_url
uploads:
avatars: configured
pages:
/profile: +show_avatar
- Minute 11: Git commit
git commit -m "Add user avatars feature"
- Minute 12: System updates
Lines changed: 4 additions to config
Version Control That Makes Sense
Old Git History
a1b2c3d Fix avatar upload bug
b2c3d4e Update tests for avatar
c3d4e5f Refactor image processing
d4e5f6g Add avatar to user model
e5f6g7h Create upload controller
f6g7h8i Update avatar styles
g7h8i9j Fix broken tests
h8i9j0k Merge branch 'feature/avatars'
DBBasic Git History
a1b2c3d Add user avatars
b2c3d4e Add date filtering to orders
c3d4e5f Increase upload limit to 10MB
d4e5f6g Add customer loyalty points
e5f6g7h Enable two-factor authentication
Each commit is a complete feature, not a code change!
The New Roles
| Old Role | New Role | What They Do |
|---|---|---|
| Product Manager | Specification Designer | Writes precise specifications |
| Developer | Config Engineer (or AI) | Refines config changes |
| QA Tester | Validation Rules | Automated in config |
| DevOps | Auto-Deploy System | Config triggers updates |
| Scrum Master | Nobody | Not needed |
Instant Rollback
Something broke? One command:
git revert HEAD
# Feature removed. System restored. 3 seconds.
A/B Testing Native
experiments:
new_checkout:
control: current_checkout.config
variant: simplified_checkout.config
split: 50/50
measure: conversion_rate
auto_winner: after_1000_conversions
Benefits Summary
| Aspect | Old Way | DBBasic Way | Improvement |
|---|---|---|---|
| Time to deploy | 2-4 weeks | 30 minutes | 40x faster |
| Lines changed | 500+ | 5-10 | 50x less |
| Files touched | 20+ | 1 | 20x simpler |
| People involved | 5-10 | 1-2 | 5x efficient |
| Rollback time | Hours/Days | 3 seconds | 1000x faster |
| Bug potential | High | Near zero | Eliminated |
The Bottom Line
Old Way: Write code → Test code → Deploy code → Fix bugs → Repeat
New Way: Specify want → Config changes → System updates → Done
See It In Action
- User: "I need to export to PDF"
- PM Specification (5 min):
export:
formats: +pdf
button: "Download as PDF"
- Git commit:
"Add PDF export" - Live in production (instantly)
No sprints. No code. No bugs. Just value delivered.
"We turned software development from a 2-week sprint into a 30-minute task."
Welcome to the post-code era where features are configurations, not code.