Just updated my smart blinds to be LLM-powered. Now when they get stuck, I sit them down and say, let’s think step by step… make no mistakes.
Daniel Barankin
Verified account This account is verified. Learn more@danielbarankin
4.2K Following 2.3K Followers 1.5K Posts
Latest posts 5
Really impressed with @balintorosz craft agents. Exploring some workflows and hacking together some ideas
Successfully migrated to @Railway for zero downtime deployment!
Hey @Replit @mattyp @amasad - as hq0 moves from being a successful vibe coded app (#1 product of the day, #2 product of the week, 3,500 users) into something production grade, my workflow is evolving and I need your help.
Up 'til now, I've built the app (frontend, middle-end, backend, infra) 100% myself exclusively using Replit. This has been an amazing experience and I'd like to keep it going!
But replit doesn't support (yet) zero downtime deployment so I need to move to @railway or @vercel or @flydotio or something
And now that its a production app and needs reliability, I need to have more people working on it. Projects is an amazing feature but it primarily protects us from messing up the codebase too bad.
We need to also be able to safely work on the @neondatabase
And we also want to safely be able to experiment and work with various APIs (and most APIs are built for truly technical developers in a pre-vibe coding world).
Since you are the leaders of safe vibe coding, my request to you is: Can you build a safety protocol that databases and API-providers can follow to enable this use case?
All that I really want to do is safely vibe code but now that the app is too big I'm not able to do that. I think @jasonlk will experience this too once his new SaaStr venture launches so spare him from this pain!
ty
Up 'til now, I've built the app (frontend, middle-end, backend, infra) 100% myself exclusively using Replit. This has been an amazing experience and I'd like to keep it going!
But replit doesn't support (yet) zero downtime deployment so I need to move to @railway or @vercel or @flydotio or something
And now that its a production app and needs reliability, I need to have more people working on it. Projects is an amazing feature but it primarily protects us from messing up the codebase too bad.
We need to also be able to safely work on the @neondatabase
And we also want to safely be able to experiment and work with various APIs (and most APIs are built for truly technical developers in a pre-vibe coding world).
Since you are the leaders of safe vibe coding, my request to you is: Can you build a safety protocol that databases and API-providers can follow to enable this use case?
All that I really want to do is safely vibe code but now that the app is too big I'm not able to do that. I think @jasonlk will experience this too once his new SaaStr venture launches so spare him from this pain!
ty
An interesting thought about yesterday's product hunt launch. It started at midnight and ended at midnight. For about 23 hours and 30 minutes we were in 2nd place, grinding hard. In the last 30 minutes we finally broke out and held first place and now we hold that title forever. There's a lesson in that.