640
Fed up with vibe coders, dev sneaks data-nuking prompt injection into their code - Ars Technica (arstechnica.com)
submitted 3 months ago by to c/technology@lemmy.world
145 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 44 points 3 months ago (21 children)

If we all followed that rule, we'd be using nothing more complex than an 8080.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 21 child comments
    •
  • [–] 19 points 3 months ago (4 children)

    True, but I would think developers should at least be following it with the code they're actually working on.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] -1 points 3 months ago (3 children)

    It's an imported library, since when are devs expected to be inspecting the source code of every library they import?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 12 points 3 months ago

    The code YOU run. If your code runs other code, that doesn't fall under this.

    "Don't ride a car unless you know how driving a car works" doesn't mean you need to understand the chemical composition of the metal in the motor parts

  • permalink
  • fedilink
  • source
  • parent
  • [–] 12 points 3 months ago (13 children)

    Well, I think it's legit to use software without understanding the code or use hardware without understanding the specifics of the logical mechanisms of the silicon. But when you're writing software, you really should know what's in your own code. Anything else is bad form in my opinion.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 13 child comments
    •
  • [–] 0 points 3 months ago (12 children)

    It's an imported library, since when are devs expected to be inspecting the source code of every library they import?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 12 child comments
    •
  • [–] 1 point 3 months ago* (last edited 3 months ago) (11 children)

    I don't like to use libraries I don't understand. Probably part why I'm not a professional developer, but it's the principle of the thing - don't put out code you can't vouch for.

    I mean, yes, it's way easier to just use the library, trust it works; but by that logic, it's also way easier to just let an llm code for you.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 11 child comments
    •
  • [–] 5 points 3 months ago (3 children)

    Probably part why I'm not a professional developer, but it's the principle of the thing

    There's no 'principle' here, that's something that simply would not be possible in any sort of large project. To suggest all professional software developers read every line of every library before using it is ridiculously unworkable.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 3 points 3 months ago (1 child)

    ...but do yoz "understand libraries" by reading every line of their code, or by reading the documentation? And only in the parts you're actually interested in?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 3 months ago

    Yeah, a general understanding is enough. But I think yeah, actually skim over the code, at least get a basic idea about how the internal methods work. Depending on what you're using the library for, it could be prudent to know more about how data structures are handled.

    Honestly, you'll probably learn something in the process.

  • permalink
  • fedilink
  • source
  • parent
  • [+] -2 points 3 months ago* (last edited 22 hours ago) (4 children)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 3 months ago* (3 children)

    Yes it can, its literally still code.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [+] 0 points 3 months ago* (last edited 22 hours ago) (2 children)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •