Contrary to what most devs belief: Most code is not shipped to hundreds of millions of users and passing the test and actually implementing a feature is worth more that drowning in backlog.
The video is spot on for codebases of products that are critical systems: payment, erp etc -> single source of truth.
Simple Crud apps/ Frontends for ecom that abstracted away the critical functionality to backend APIs (ERP, shop system, payment etc) benefit from vibe slop vs no shipping cadence
You're producing technical debt. At some point you will invest more time fixing the vibe slop than it would have cost you to do the work yourself in the first place. A lot of vibe-coding just feels like shifting responsibility and resources from "development" to "incident response".
I built /dev/push because I wanted to offer a more streamlined UX, closer to what Vercel offer.
I am planning on adding more runtimes (there's a PR for Bun for example), support for custom containers and support for Docker Swarm, allowing you to manage multiple servers with a single instance.
I think you can get stronger by building your own identity (rather than "like vercel") - starts with the headline/tagline and pitch in a way that stands on its own.
"Open source X alternatives" are dime-a-dozen and put a limit on what you can be in the eyes of users. It also sets expectations such that differences easily become disappointment. Not having a global CDN can otherwise simply be out of scope but can be "missing feature" when pitched as an alternative to an established service.
The trouble I have is that when I see a headline like this on hackernews my first thought is always "huh.. so what are netlify and vercel?" Maybe most people on here already use those daily but not being in web development I usually don't.
I don't think Coolify does that either, it was just one of the first modern PaaS that got traction after Dokku and CapRover which I consider a bit older and less modern, no GUI for example, but people seem to want a GUI for deployment management.
