Depending on the scale. If you ask Clause to one-shot an app from a nebulous description, you get a prototype which you would understandably loathe to own the code of. If you plan carefully and limit the scope, you get code that you understand, can approve of, and are okay owning further down the line.
replyI spent two and a half hours writing up a detailed outline for a small webapp. Claude popped it out in one shot 100% working., I added features after but the time you spend on a good outline saves hours later.
replyAt what point is liability the only "job" left for humans?
replyI think it was tor.com that last year had a story where the newbie hired for the corporate HR dept ended up being the last human left after all others were replaced.
replyAh, here we go, courtesy of google-ml: '"Human Resources" by Adrian Tchaikovsky, published on Reactor[...] https://reactormag.com/human-resources-adrian-tchaikovsky/ '
Presumably, every company that has non-LGPL CC code in production wants to own it...
reply"Own" as in "be responsible for". Nobody is too keen to own a pile of semi-working trash, and extensive vide-coding can produce such piles easily.
replyNot sure why this is being down voted. Outsourcing work doesn't also outsource accountability.
replyAnyone can produce low-quality code, with or without AI. Agents have gotten exceptionally good however, and everyone should be including them in their workflow if they're able to.
replyAgents are more prolific. As with any power tool, they increase both your ability to build and to wreak havoc, depending on how you handle them.
replyYea, that is how I meant it.
reply> "Own" as in "be responsible for". Nobody is too keen to own a pile of semi-working trash
replyAnd yet that was the state of software at every company I worked at before FAANG, and even a good amount there...