A pretty light-grey comment as I came across it. Maybe I’m missing something odious about it? People downvote this, but as a VERY skeptical AI skeptic, it’s exactly the sort of use case that makes sense to me:

A) Low-stakes application with

B) nearly no attack surface that

C) you don’t use consistently enough to keep in your head, but

D) is simple enough for an experienced software developer to do a quick sanity check on and run it to see if it works.

Hell, do it in a sandbox if you feel better about it.

If it was a Django/Node/rails/Laravel/…Phoenix… (sorry, I’ve been out of my 12+ years web dev career a short 4 years and suddenly realized I can only remember like 4 server-side frameworks/environments now) application, something that would run on other people’s devices, or really anything else that produces an executable output, then yeah fuck that vibe coding bullshit. But unless you’ve got that thing spitting out an SPA for you, then I say go for it.

Yeah I feel like Claude Code is basically tailor made for a use-case like this. Where:

* I have forked some public repository that has kept up with upstream (IE; lots of example code to draw from)

* Upstream is publishing documentation on what's changing

* The errors are somewhat google-able

* Can be done in a VM and thrown away

* Limited attack surface anyway.

I think you're downvoted because the comment comes across as glib and handwavy (or not moving the discussion forward.. maybe?), and if it was a year ago I would probably argue against it.. but I think Claude Code can definitely help with this.

It just didn't exist as it does in 2023~ or whenever it was that I originally started having issues.

---

That said: it shouldn't be necessary. As others in this thread have articulated (well, imo) sometimes software is "done" and Hugo could be "done" software, except it's not; so the onus is on the operator to pin their definition of "done" version.. which is not what you'd expect.