Most of ours are internal-only because we don't need or want to release them to the public. Sometimes there isn't much of an UI - they're one-off vibe-coded apps for specialized functions within our organization meant for a small number of people. Beginning to think of the vibe-coded apps akin to spreadsheets with lots of macros.
I don’t trust the process enough to commit to it for user facing services, but I regularly find toy use cases and itches to scratch where the capability to crank out something useful in 20 minutes has been a godsend.
>Beginning to think of the vibe-coded apps akin to spreadsheets with lots of macros.
Maybe not anymore, as it's pretty simple to take a "vibe-coded" repo and have a modern agent change it according to your specs. Re-vibe it from time to time, and there goes your technical debt. If the app could be vibed at a random date, chances are it will keep be inside the capabilities of future models / agents /etc.
You might have forgotten the language but I bet it must have had some influence on how you think or write programs today. I don’t think the value of learning Prolog is necessarily that you can then write programs in Prolog, but that it shifts your perspective and adds another dimension to how you approach problems. At least this is what it has done for me and I find that still valuable today.
Yeah, the problem we found is that when we switched to non-American English, Siri expects us to be speaking it as well... and messes up what she understands.
