655
fuck you bill (lemy.lol)
submitted 4 months ago by to c/programmer_humor@programming.dev
93 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 55 points 3 months ago (8 children)

I've seen the comments AI adds and yeah... No.... It's often pointing out the obvious or even in some cases just misleading.

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

    Sounds like what a lot of beginner programmers do as well.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 17 points 3 months ago* (last edited 3 months ago) (1 child)

    Not just beginners unfortunately. One of the things I have to almost always teach to new colleagues, even experienced ones, is to put at least some minimal effort into making the code itself readable instead of relying on comments as crutches. Just basic things like picking proper names for variables and functions.

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

    a = aa + aaa .* a3(A(aa).a2);

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

    I told my boss I wouldn't use AI to help write code and sign off on the commits with my name. He told me to use it to write the documentation... it was bad. Essential concepts were not mentioned and obvious shit was explained five times in slightly different phrasing. I am now writing our documentation as an obsidian vault myself again.

    I only have it compile a change log from the commit messages of commits and merges on the main and development branch. I know our commits are well written (because I established the standards for them in our repo myself) and that's concrete and rigid enough that it can't fuck it up enough to matter.

    But honestly there are build tools that could do that for me, I don't need to buy tokens for that.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 6 points 3 months ago*

    honestly there are build tools that could do that for me, I don't need to buy tokens for that.

    Yes. This is where every "have you tried Agentic AI?" conservation lands, for me.

    They tell me I could pay daily, for worse results, to give up the bash script that has worked perfectly for five years. Oh, gee. Tell me more! Haha.

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

    Agreed it's why if I'm asking for llm assistance I will generally start with a design for a component and ask it to follow that and comment accordingly usually leads to much better results than blanket asking it to do something for you

  • permalink
  • fedilink
  • source
  • parent
  • [–] 0 points 3 months ago (2 children)

    You can add instructions to not comment, you can also have it explain what it does at every step, not everyone just doesn't care about learning. It can be a very effective teaching tool if you use it that way. 🤷

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

    AI is a terrible way to learn something. It will do something wrong, explain it incorrectly, and you will have no idea.

    AI is only useful if you are able to spot and correct the mistakes it makes. Because it will make mistakes.

    Very effective teaching tools already exist if you want to learn.

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

    "You'll have no idea" until it doesn't work lmfao

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

    Someone hasn't done enough debugging in their life. I wish the lesson be as painless as possible

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

    I'm definitely still a noob but I've done hundreds of hours of debugging on code in the past few months, and my job for the past 8 years is basically to troubleshoot issues, though the past year I got to start doing devops/code work on the side.

    Its fine though, I get why you guys are scared.

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

    Then you should know that code not working is the absolute easiest fuckup to catch. It's literally not one to be concerned about.

    One in a million chance of an edge case that doesn't throw an error at all, but does something unexpected? Good luck if you don't know how the system works.

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

    I do and please name a single human written program that doesn't have a fuck up edge case that isn't literally just hello world.

    Neither humans nor AI generally write flawless code

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

    Neither humans nor AI write flawless code, but if you actually understand how your code works, you'll have a significantly easier time finding that edge case, with or without AI.

    If you only ever let your AI do everything for you, you're at its mercy for debugging.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 0 points 3 months ago

    Out of the box yes this is true, but:

    1. Custom instructions go a long way
    2. Review the code yourself, tell it what to fix, and it will fix it. For me it often takes like 5 rounds of this before the code is fully polished to the point I'm proud of it. And you know what? It's still MULTIPLE times faster than typing code by hand. And at least for me, the quality is higher, because I have 12 different agents that review the work too and they catch additional issues that even I missed.

    If you or others ship shitty code don't blame the LLM, the issue is entirely the engineer using it wrong

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

    So... indistinguishable from the statistical mean of human generated comments.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •