Implemented a platform in 90s (specs built by drag-n-drop), then in 10s - server-client real-time collaborative (drag-n-drop). And finished a brief POC ref implementation a few days ago (HTML/JS/Java) - for AI era.
Two stages: vague app idea + "compilation.md" -> human readable/amendable "objective" text/script -> 100 % deterministic interpretation engine (~10MB no installation executable - runs like a simple web server).
App idea #1: "create a simple CRM app" - 30 seconds - the app is live:
multiple (6) foreign keys: Country-City, Department-Teams, Project-Milestone.
CRUD ACID app. Customization scripts are optional.
"One sentence from me[user/dev] → 50 lines of script → working multi-key CRM → user navigates, filters by 6 dimensions, inserts records, views records. Zero SQL. Zero code. Zero configuration beyond the script."(C Claude)
App idea #2: "give me something similar... I was thinking of container for my downloaded papers(?) by authors, keywords, ** or my wife receipts container - purpose, date, bank, card - whatever. Your choice : which app would you think of?"
Claude: "Papers container — hands down. More interesting architecture. Here's why:
Wife's receipts is a flat single-key app — Purpose, Date, Bank, Card. Simple but boring.
Papers has a natural rich hierarchy:
Authors — who wrote it
Keywords/Topics — what it's about
Journals/Sources — where it came from
Stars/Rating — how important to you
The paper itself — PDF as a leaf with mediaBox"
another 30 seconds - it's live. (shown in the clip)
I swear I did not know it's called SDD...
Implemented a platform in 90s (specs built by drag-n-drop), then in 10s - server-client real-time collaborative (drag-n-drop). And finished a brief POC ref implementation a few days ago (HTML/JS/Java) - for AI era. Two stages: vague app idea + "compilation.md" -> human readable/amendable "objective" text/script -> 100 % deterministic interpretation engine (~10MB no installation executable - runs like a simple web server).
App idea #1: "create a simple CRM app" - 30 seconds - the app is live: multiple (6) foreign keys: Country-City, Department-Teams, Project-Milestone. CRUD ACID app. Customization scripts are optional.
"One sentence from me[user/dev] → 50 lines of script → working multi-key CRM → user navigates, filters by 6 dimensions, inserts records, views records. Zero SQL. Zero code. Zero configuration beyond the script."(C Claude)
App idea #2: "give me something similar... I was thinking of container for my downloaded papers(?) by authors, keywords, ** or my wife receipts container - purpose, date, bank, card - whatever. Your choice : which app would you think of?"
Claude: "Papers container — hands down. More interesting architecture. Here's why: Wife's receipts is a flat single-key app — Purpose, Date, Bank, Card. Simple but boring. Papers has a natural rich hierarchy:
Authors — who wrote it Keywords/Topics — what it's about Journals/Sources — where it came from Stars/Rating — how important to you The paper itself — PDF as a leaf with mediaBox"
another 30 seconds - it's live. (shown in the clip)
What do you guys think?