Comment

Comment on A Vibe Coded SaaS Killed My Team

Alphane_Moon@lemmy.world ⁨4⁩ ⁨months⁩ ago

I could place orders without giving my contact details or payment.

This isn’t a “vibe coding” issue. This is just basic laziness/fraud. Even with vibe coding, you can get by if the project is simple, you know the business/operational elements of the domain, you aggressively test the solution and are aware of any least common edge cases.

source

Sort:hotnew top

TORFdot0@lemmy.world ⁨4⁩ ⁨months⁩ ago
Since when has vibe coding ever been done by some one like that and not the nepo baby son of the CFo who is good at computer

source
- Alphane_Moon@lemmy.world ⁨4⁩ ⁨months⁩ ago
  I’ve used vibe coding in a project where the coding part was small (20% of the total project, with the complex stuff being the remaining 80%) and it had relatively straightforward workflow that could be tested and accounted for without strange edge cases.
  
  It’s not only nepo/conmen types who use vibe coding.
  
  source
partofthevoice@lemmy.zip ⁨4⁩ ⁨months⁩ ago
Vibe coding is a self perpetuating feedback loop of hallucinations. The more complex the project gets, the worse the problems. The agent reads its own prior code, which biases it to the prior approach. That bias just pushes issue further, buries them deeper, and you don’t find out until the product is done enough to actually look at it.

I knew a guy who wanted his vibe coding project to display the page count in a PDF. I showed him a super simple python script to do it, but it wasn’t usable for him because his shitty implementation was so unmanageable, so grotesquely over and under engineered at the same time, … he rather spent hours trying and failing to get the AI agent to implement my feature for him.

source
jj4211@lemmy.world ⁨4⁩ ⁨months⁩ ago
It’s pretty much a vibe coding issue. What you describe I can recall being advocated forevet, the project manager’s dtram that you model and spec things out enough and perfectly model the world in your test cases, then you are golden. Except the world has never been so convenient and you bank on the programming being reasonably workable by people to compensate.

Problem is people who think they can replace understanding with vibe coding. If you can only vibe code, you will end up with problems you cannot fix and the LLM can’t either. If you can fix the problems, then you are not inclined to toss overly long chunks of LLM stuff because they generate ugly hard to maintain code that tends to violate all sorts of best practices for programming.

source
- Alphane_Moon@lemmy.world ⁨4⁩ ⁨months⁩ ago
  For sure, I am talking about smaller projects where programming elements are relatively low key and critical parts are the business logic and how it impacts UX/UI and use case flows.
  
  I was between projects and I needed money so I accepted a project from a repeat client where I knew 80% of it very well (and how to implement it), but there were parts that I vibe coded (albeit they were simple enough that I could understand the logic of what I was deploying even though I don’t know how to code).
  
  The contract size was simply too small for me to get a subcontractor, I would be giving them most of payment (while doing 80% of the work).
  
  I think it’s fair to use vibe coding in such situations.
  
  I would not risk vibe coding in a situation where I felt I would be undermining the clients’ project (I want repeat clients and I don’t want to have to spend time fixing things for free).
  
  source