22
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Feb 2024
22 points (100.0% liked)
Programming
13361 readers
1 users here now
All things programming and coding related. Subcommunity of Technology.
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 1 year ago
MODERATORS
I think that's a great way to handle it. It's a tool in your belt. A lot of this reminds me of when Intellisense entered the scene. Some people are saying it's stupid and it'll slow us down, others are saying it's going to replace us. In reality, it's exactly like what you said. If it helps you then absolutely use it, but don't blindly trust it. Use it to help remind you or think of new ways to do it, but also let's remember how many times we've gone down the wrong path using intellisense because it thought we wanted this instead of that.
Honestly thinking of it like intellisense reminds me of what one of my professors did. He barred us from using it in my first semester, we had to write everything in vim. He said pretty much the same thing as you, that it's a tool we get to use later to speed us up, but we need to understand what it's doing first before we can use it.
Well, the problem is you don't know what you don't know. One of the first example tasks in the paper was regarding implementing a symmetric cipher. Using a weak cipher was recommended by AI tools sometimes, these developers didn't know that some ciphers were weak. Additionally, even when the AI tool recommended a strong cipher, such as AES, it generated code that screwed up an implementation detail (failing to return the authentication tag), making the result insecure. And the user didn't know it was wrong because they didn't know it was incomplete.
There's no substitution for domain specific knowledge. Users who were forced to use traditional tools got the answer correct significantly more often because they had to read, process, and understand the documentation for the libraries, which meant they understood why the symmetric cipher was the way it is, and what additional information needed to be reported and why.