Cast by jrf
Show the cast this replies toi think for you it's a tool for most ppl it's a mess maker and similarly i will still use vibecoding software to work on frontend, which i can reliably do without breaking things (if i check out a branch and make a pull request) related: farcaster.xyz/jrf/0xdedd20a0
1 reply
This is accurate, I think, both what you said about it being a tool for me and a mess maker for most people, and the statement about real devs not really understanding the term vibecoding. And I fall in a weird category, I taught myself BASIC from a book at 4, and took classes off and on through the end of hugh school, then got my COSC degree in more old school type programming (in PASCAL, C, C++, LISP, assembly, etc), but my career has been in infrastructure, sysadmin, networking, database, cloud based devops. Most of my programming has been either scripting or small projects in work, and more backend type things with raw HTML or CLI as front end. So I tend to approach everything as a tool for a task.
fully appreciate it and instead of a *tool*, vibecoding apps are telling users they can completely handle auth, architecture, frontend, backend, any integration, any new feature...? in reality it's a subscription that creates the illusion of progress and scaffolding, but it's just a mess if you can't evaluate its choices