3 ms·

"Two weeks of warranty" jumped out at me. That's like "you have two weeks to find the thing we broke, or else we aren't responsible for it." In my experience, a

"Two weeks of warranty" jumped out at me. That's like "you have two weeks to find the thing we broke, or else we aren't responsible for it." In my experience, a good bug can hide for months more than two weeks! My codebases are definitely not in the target demographic for this service, though, and maybe if I were in the target group (bunch of LLM slop, trying to dig out of the hole, presumably no shipping product or existing userbase yet) the proposition would appeal to me.

shoo 3mo ago
If the client has an extensive suite of automated tests assessing if the software is meeting its requirements, it should be possible for them to flush out most regressions within minutes or hours, not weeks. If the client hasn't invested in setting that up, the resulting situation is the clients' responsibility.
- dpark 3mo ago
  If the client has that, they definitely don’t need an external party to ask Claude to do code cleanup for them.
  - zie1ony 3mo ago
    Unless tests are also vibecoded.
zie1ony 3mo ago
This is a fair point. But these days bugs are not so scary anymore, so a client can vibecode a fix faster then getting me to fix it. Of course if Opus can't figure it out, I would always try to help. I have never left a client alone, warranty or not. This is just how I was raised.
- Carrok 3mo ago
  > bugs are not so scary anymore Umm, what? Bugs can cause user data loss in production, or total system outages, or a slew of other Really Bad Things. How are you planning to vibecode your way out of that after the fact?
- fuzzythinker 3mo ago
  How do you tell if the bug was your responsibility vs. something they changed after?