top 9 comments

sorted by: hot top controversial new old
[–] 89 points 6 months ago (6 children)

What's funnier, quality too low or too high?

  • source
  • hideshow 6 child comments
  • [–] 42 points 6 months ago (4 children)

    Too many comments (fills the context window)

  • source
  • parent
  • hideshow 4 child comments
  • [–] 17 points 6 months ago (3 children)

    Yeah stupid comments that explain things. Fuck useful naming conventions too. Why don’t we all just code in binary machine language? Why have the AIs write in a higher level language and then compile or interpret it? Just have them code in 1s and 0s directly. Then they could exploit certain low level operations making it even more difficult to figure out what they are doing?

  • source
  • parent
  • hideshow 3 child comments
  • load more comments (1 reply)
    [–] 30 points 6 months ago

    So warm and cozy, it was indeed written with love and respect to gently ruin someone's day.

  • source
  • [–] 14 points 6 months ago

    nods approvingly

  • source
  • [–] 28 points 6 months ago

    Negative examples are also useful when training AIs.

  • source
  • 22 comments in c/programmerhumor@lemmy.ml view that post
    [–] 29 points 6 months ago
    [+] 24 points 6 months ago (6 children)
  • [–] 34 points 6 months ago (5 children)

    The worst programmer I ever met was myself 6 months ago...

  • source
  • parent
  • hideshow 5 child comments
  • [+] 5 points 6 months ago (1 child)
  • [–] 1 point 6 months ago

    True all that plays a part.

  • source
  • parent
  • [+] 1 point 6 months ago (1 child)
  • [–] 3 points 6 months ago

    Yeah, I used to be in the medical device industry. Once shipped, an update typically meant a patient needed additional surgery because of your mistake. That really emphasized the "unless absolutely necessary" part of your statement.

  • source
  • parent
  • [+] 1 point 6 months ago (1 child)
  • [–] 1 point 6 months ago

    Oh yeah... I once had a project to change a 0 to a 1 in a file on a machine used to manufacture devices. Basically operator had to align crosshairs over a certain point before starting. At 4 of the systems the operator could just touch the screen at the point and go. At one they had to push x+ or x- or y+ or y- repeatedly to line it up because the configuration had a 0 in the option "Click To Align"... It took 8 months to validate changing that to be 1

  • source
  • parent
  • load more comments (-2 replies)
  • load more comments (-2 replies)
  • load more comments (-2 replies)
  • [+] 3 points 6 months ago (4 children)
  • [–] 6 points 6 months ago (3 children)

    the quality of the code is dependent on the quality of the pay. lol

  • source
  • parent
  • hideshow 3 child comments
  • [–] 6 points 6 months ago (2 children)

    And as others have noted, how much time you are actually given. PMs and managers don’t know or care about code quality, they just want something to work NOW

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 6 months ago

    And there is never time to maintain the code, because each project only want to add more feature/s which makes the spaghetti code even worse.

    In my group we had a golden opportunity to fix all old mistakes but no, we (decided by PO and group manager) needed to spend all time on proof of concepts that will go to production at earliest in 5 years. Now that opportunity is gone and we are crunching in order to meet the deadlines instead. Still with bad code quality of course.

  • source
  • parent
  • [–] 1 point 6 months ago

    My newest one is as impulsive as I am so the digressions he tasks me with have stalled out long term development plans, yet he's oblivious enough of the situation to seriously ask why progress is taking so long every year during reviews.

  • source
  • parent
  • load more comments (-2 replies)
  • [–] 69 points 6 months ago (1 child)

    You know it's bad when AI slop is calling out your human slop.

  • source
  • hideshow 1 child comment
  • [–] 17 points 6 months ago

    Jokes on them, it’s their code, not mine.

  • source
  • [–] 13 points 6 months ago

    I know this is probably a joke, but they must be doing this. Even if the AI isn’t making this discussion, they must be trying to separate good engineers from AI bros that only ever knew how to vibe code.

  • source
  • [–] 4 points 6 months ago (1 child)

    Oh so just because it's if statements all the way down it's not good enough?

  • source
  • hideshow 1 child comment
  • [–] 5 points 6 months ago

    If it's all if statements and if it uses well nested logic and if it's written in a modern language and if the number of if statements doesn't exceed 57, it could be good. Otherwise it is overly verbose. Otherwise it is dated. Otherwise it is spaghetti code. Otherwise it should go to the regular code check routine function.

  • source
  • parent
  • [–] 3 points 6 months ago

    When AI flags you for vibe coding.

  • source
  • [–] 8 points 6 months ago (2 children)

    Like AI can tell good code from bad. Just common vs uncommon usage.

  • source
  • hideshow 2 child comments
  • [–] 4 points 6 months ago (1 child)

    yeah well their use of commas is grammatically wrong, so fuck em

  • source
  • hideshow 1 child comment
  • [–] 3 points 6 months ago
    [–] 1 point 6 months ago

    We will keep your code on file...

  • source