I tried it in DataGrip on a messy database. It hallucinated about which tables and columns to use. Had better results using Claude in the terminal and having it give me the SQL to run.
The technology is only half of the puzzle; the other half is the availability of the data. For example, many toll roads use license plate readers. Police cruisers may also read a license plate.
Flock the technology would be less of a problem if it had reasonable guards around access, such as requiring search warrants for each query, in each jurisdiction the results touch.
It's very amusing how for a decade, The Way (TM) has been "move fast and break things", but now with LLMs it's suddenly "woah, AI is moving so fast, it's going to break things!"
> I agree, I think this false dichotomy between using LLMs and caring about quality/reliability needs to stop.
It's not just a false dichotomy, it's intellectual dishonesty. It wasn't that long that conversations about code quality, technical debt, etc were on the front page of HN on the regular. Whether it was coding bootcamp grads who had just enough confidence to be dangerous, "just ship it!" cargo culters, or the product of management breathing down the necks of otherwise good developers, there's plenty of "human slop" running in production across servers worldwide.
I don't think it's a matter of justifying any evil, so long as the argument is made in good faith. Pushing the idea of bad code emerging from AI isn't a good faith argument.
OpenClaw isn't the target anymore, Hermes is. It may have been the first, in the same sense that new social networks were often referred to as Facebook-clones, not Myspace (or Friendster) clones.
reply