11–20 of 168 posts
I was almost expecting to hear that it made the job too easy. This kind of work is perfect for vibe coding. But you should be the one doing it.
You have to drive the LLM, you cannot let it drive. Therefore you still need to code. There is no best practices anymore, no proper process, no meaningful back and forth. There absolutely is and you need to work with the tools to make sure this happens. Else chaos will ensue. Been working with these things heavily for development for 6-12 months. You absolutely must code with them.
Ah yes a supabase backed, hallucinated data model with random shit, using deprecated methods, and a copy paste UI. Zero access control or privacy, 1% of features, no files uploading or playback or calling.
“Can you scale this to 1M users by end of the week? Something similar to WhatsApp or Telegram or Signal”
Sybau mf
You have to drive the LLM, you cannot let it drive. Therefore you still need to code. There is no best practices anymore, no proper process, no meaningful back and forth. There absolutely is and you need to work with the tools to make sure this happens. Else chaos will ensue. Been working with these things heavily for development for 6-12 months. You absolutely must code with them.
Their issue is their clients trying to push AI garbage, not themselves. And that's a business professionalism boundary issue, not an AI one.
We’re in the geocities phase of LLM, mostly trash, very basic, but eventually, people will either get bored and go back to whatever it is they were doing or actually use the tools for useful and productive work. As for the feelings that using LLM has when it one shots your project start (and does a pretty good job), have a German word: Automatisierungskummer (automation sorrow) • Kummer is emotional heaviness, a mild…
Its hard to know what things will look like in 20 years but people may miss the time when AI cost nothing, or very little, and was less fettered. I think probably not- it would be like being nostalgic for really low-res, low frame youtube videos, but nostalgia is pretty unpredictable and some people love those old FMV games.
This article is not about vibe coding per se, it's about not having strong boundaries between you as the developer, and your client. You should not be allowing the client to dictate how you work, much less them having the permissions to merge in code. This was true before AI too, where clients might say, do X this way, and you should simply say no, because they are paying for your expertise*. It's like hiring a plumb…
I guess that, with vibe coding, it is very easy for every client to become like this.