I see no difference there except speed at the cost of whatever little understanding may have been gained by the manual inspection between steps.
I see no difference there except speed at the cost of whatever little understanding may have been gained by the manual inspection between steps.
Personally I've found LLM's suck at multi-threaded applications. (Because I've been tempted by the ~agentic loop~ and been burned. Then I hand code the core logic and all is well).
Woe to the developer who tries to prompt their way through this.
But seriously, lots of apps are just glorified NextJS apps which have tons of training data. Something like rust would likely churn out nonsense that compiles eventually but isn't optimal.
Agreed with the caveat that I think if you know what you're doing and are very cognizant, LLM generated Rust is amazing. I feel like it's hard compilation requirements gives a guardrails for a LLM and if it compiles, you're pretty safe against memory issues.
Sometimes I mess around with prompts just to see what I get back, more often than not, it's mostly a waste of time. God forbid you use it to refactor anything.
x=ctrl-c("output error report")
eval(ctrl-v(x))
sleep(10)
user("Input...")
something like this?