I just vibe-coded a complete GUI control panel for my dad's painting gallery. Didn't write a single line of code.
Backstory:
I built the gallery a year or so ago by-hand, to facilitate family and friends browsing and choosing any paintings they want. It has filter tags, resizing, and a sprinkling of useful metadata.
At its heart is a single .JSON object containing all 800+ items:
jsonListings = [
{
"folder": "./box-a",
"store": "Box A",
"img": "2521",
"descrip": "",
"note": "Corina",
"price": "",
"claimed": "true",
"tags": [
"matted",
"structure"
]
},
{
"folder": "./box-a",
"store": "Box A",
"img": "2522",
"descrip": "",
"note": "",
"price": "",
"tags": [
"structure",
"matted"
]
},
/Backstory
So I have been jonesing for a control panel that
All it did was ask me for my data file and it
The whole endeavor took maybe two hours - and 1.5 of those hours was me asking for aesthetic tweaks.
Here it is. One page, one file:
What a time to be alive. Also: damn I'm glad I'm about to retire...
And before you ask: why a .js data file, and not a proper database? Because I don't trust databases. Or, more accurately, I don't trust webhosts. Even more accurately, I don't trust myself to remember, a year later, how it works. Complex technology is fragile, and it rots. Versions change, my brain forgets how stuff was built, I lose intrest in maintaining/troubleshooting it. I've have more than one project get bricked because my webhost shuttered its doors, or the database became incompatible and it would take too much work to troubleshoot. And I like self-contained, portable, discrete web apps.
Totally agree. As with all things: the right tool for the right job.
Useful as it may be for many other things, I would not use an internal combustion engine to clean my ears. There are safer, more appropriate tools for that.
I did have to learn to work around its foibles. It would never admit it couldn't do something. Instead things would get worse and worse accompanied by declarations like "now I've nailed it!" so it was important to keep checkpoints to which one could retreat. I learned to never let it touch my code directly, as it would sometimes leave out things that weren't relevant to the issue at hand, me finding out about this much later. But on the whole it was a huge gain, speeding things up a factor of at least ten and producing a higher quality product. It didn't hurt that it kept reminding me what a genius I was.
I suppose things are better now but I've already had more than enough programming for one lifetime.
The checkpoint advice is especially useful. AI can save a lot of time, but keeping a working version to fall back on seems essential when it starts making changes across a project. I also think being able to explain what you want in plain language is a big part of what makes these tools so useful.TL;DR: Not a question, just marvelling at AI's capabilitiesI'm old and I want to get stuff done. I have other hobbies than programming web applcations.
I just vibe-coded a complete GUI control panel for my dad's painting gallery. Didn't write a single line of code.
Backstory:
I built the gallery a year or so ago by-hand, to facilitate family and friends browsing and choosing any paintings they want. It has filter tags, resizing, and a sprinkling of useful metadata.At its heart is a single .JSON object containing all 800+ items:
Every time someone asks for a painting I've got to go in and update this .js file manually, then upload it to the server. A single missed comma or quote, and the whole thing bricks. My brother just asked for a dozen.jsonListings = [ { "folder": "./box-a", "store": "Box A", "img": "2521", "descrip": "", "note": "Corina", "price": "", "claimed": "true", "tags": [ "matted", "structure" ] }, { "folder": "./box-a", "store": "Box A", "img": "2522", "descrip": "", "note": "", "price": "", "tags": [ "structure", "matted" ] },/Backstory
So I have been jonesing for a control panel that
I was on the verge of asking my PHP friend how much he'd ask to do it for me, when I thought I'd give ChatGPT a shot at it.
- eliminates crashy typos and discourages uncrashy typos.
- works directly online, so I don't have to laboriously edit it in Notepad, then save the file, then upload it to the server every time.
All it did was ask me for my data file and it
It did this all on its own without being asked.
- built an entire CRUD (Create, Read, Update, Delete) interface to operate it,
- guessed the field types, including the multi-select tags I was using for filtering,
- created a one-time setup file so I could create my own a password access,
- implemented the list/line-item layout, a keyword search, a filter, two-level save, cancel, dupe and delete,
- supplied user prompts before committing to data-altering operations,
- left my data file exactly as-is, in human-friendly format with my inline, comments, in case I want to (or have to) fall back to operating it manually,
- used the proper PHP methods to encode the data, so it handles things like quotes gracefully (being a flat data file, it is also immune to SQL injection attacks),
- troubleshot a compatibility problem with the version of PHP my webhost uses. Replaced the 8.0 function with one that works with my webhost's PHP version,
- produced a README.TXT file to tell me exactly how to implement it and run the setup.
The whole endeavor took maybe two hours - and 1.5 of those hours was me asking for aesthetic tweaks.
Here it is. One page, one file:
What a time to be alive. Also: damn I'm glad I'm about to retire...
And before you ask: why a .js data file, and not a proper database? Because I don't trust databases. Or, more accurately, I don't trust webhosts. Even more accurately, I don't trust myself to remember, a year later, how it works. Complex technology is fragile, and it rots. Versions change, my brain forgets how stuff was built, I lose intrest in maintaining/troubleshooting it. I've have more than one project get bricked because my webhost shuttered its doors, or the database became incompatible and it would take too much work to troubleshoot. And I like self-contained, portable, discrete web apps.
Fortunately, it also makes that easy by providing a downloadable, versioned zip file with each iteration. They unzip over top of the existing files, so only one production set of files, but if anyone of them doesn't work, I just unzip the previous version over top of it.
Oh yeah. One other feature it added without being asked. I created a "data backups" folder and auto-saves a time-stamped version of the data before making any changes to it.
It reminds me of Shakespeare's The Tempest or the sci-fi story Forbidden Planet, where the power of AI is harnessed by the Id, and we are no more.
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | Vibe Coding Sparked a Love of Reading in My Classroom | 0 | 8.19 | 24-06-2026 |
| 2 | Reckoning With The IP Risks Of Building Vibe-Coded Products | 0 | 12.8 | 16-10-2026 |
| 3 | Vibe Coding Security: Risks, Incidents & How to Avoid | 0 | 11.65 | 30-07-2026 |
| 4 | The rise of vibe lawyering | 0 | 5 | 29-06-2026 |
| 5 | Building The Future Of Software In The AI-Native Era | 0 | 17.78 | 19-11-2025 |
| 6 | Will anybody use AI as much as coders do? | 0 | 7.09 | 30-08-2026 |
| 7 | How Cadence Agentic AI Will Transform RF Design Productivity | 0 | 10 | 13-07-2026 |
| 8 | Enterprise Vibe Coding: Best Practices & Key Considerations | 0 | 7.59 | 29-07-2026 |
| 9 | Beyond the Hype: How AI Can Reshape Government Operations | 0 | 10 | 28-05-2026 |
| 10 | This Dev Built an Office Suite Because His Wife Kept Going Back to Microsoft Office | 0 | 11.94 | 14-10-2026 |