Live data from Hacker News

Potential issues in curl found using AI assisted tools

mastodon.social

201–203 of 203 posts

Re: Potential issues in curl found using AI assisted tools

#201
post #183

To anyone who thinks about our current situation for than a few minutes, AI is * Clearly useful to people who are already competent developers and security researchers * Utterly useless to people who have no clue what they're doing But the latter group's incompetency does not make AI useless in the same way that a fighter jet is not useless because a toddler cannot pilot it.

> * Utterly useless to people who have no clue what they're doing I disagree. I'm making a board game of 6 colors of hexes, and I wanted to be able to easily edit the board. The first time around, I used a screenshot of a bunch of hexagons and used paint to color them (tedious, ugly, not transparent, poor quality). This time, I asked ChatGPT to make an SVG of the board and then make a JS script so that clicking on a…

You sound at least somewhat experienced. You knew you wanted an SVG and that Javascript could be inserted into it. That's a pretty reasonable design starting point.

Re: Potential issues in curl found using AI assisted tools

#202

Earlier quoted context omitted.

> “A good tool in the hands of a competent person is a powerful combination,” says Daniel Stenberg.

Daniel Stenberg has been vocal about AI generated patches in the past, and it's interesting to see him changing course here. https://news.ycombinator.com/item?id=38845878 https://news.ycombinator.com/item?id=43907376 https://media.ccc.de/v/froscon2025-3407-ai_slop_attacks_on_t...

He's been against people submitting garbage they don't understand, not AI as a whole.

Re: Potential issues in curl found using AI assisted tools

#203

This is exactly what I'd want from an 'AI coding companion'. Don't write or fix the code for me (thanks but I can manage that on my own with much less hassle), but instead tell me which places in the code look suspicious and where I need to have a closer look. When I ask Claude to find bugs in my 20kloc C library it more or less just splits the file(s) into smaller chunks and greps for specific code patterns and in t…

> When I ask Claude to find bugs in my 20kloc C library it more or less just splits the file(s) into smaller chunks and greps for specific code patterns and in the end just gives me a list of my own FIXME comments (lol), which tbh is quite underwhelming - a simple bash script could do that too. Here's a technique that often works well for me: When you get unexpectedly poor results, ask the LLM what it thinks an effec…

If you don't edit this prompt, how is it any better than the LLM generating the same context for itself on the fly in "thinking mode"?
Post reply on HN