My current thing with LLM’s is, if they are going to replace me, why wouldn’t it first somehow replace stuff like
- build tools
- bundling scripts
- ci/cd processes
🤔
My current thing with LLM’s is, if they are going to replace me, why wouldn’t it first somehow replace stuff like
- build tools
- bundling scripts
- ci/cd processes
🤔
@Anneke You happen to name things where we want to be consistent, deterministic, and (somewhat) transparent instead of being opaque and do wildly different things based on a randomly assigned seed or the tone of voice of your prompt 😅
The closest thing I've seen to what you're describing is GitHub's Agentic Workflows, which allows you to schedule an agent to complete a prompt. Could be interesting to update dependencies (and follow upgrade guides), for example.
@timsev well I wasn’t asking a real question, I am just feeling a discrepancy of how we have made our code less simplistic by throwing multiple meta layers over it, and then people seem happy to AI the stuff that I think is simpler away but keep the (to me) convuleted part. I get wanting to be consistent. But I don’t get the feeling a lot of vibe coders really care that much about the transparency already :)
(I saw a preso about agentic workflows in github doing accessibility tests)