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.

▲

jcims a day ago | parent | next [-]

This is my experience.

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.

This resonates.

▲

SecretDreams a day ago | parent | prev [-]

> Beginning to think of the vibe-coded apps akin to spreadsheets with lots of macros.

These things normally die a sigmoidal death after the creator changes jobs.

	▲	NitpickLawyer a day ago \| parent [-]
		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.