• Dizzy Devil Ducky@lemm.ee
    link
    fedilink
    English
    arrow-up
    18
    arrow-down
    27
    ·
    10 months ago

    I hope I learn some day how to code a bug in python that will not show up in any error messages and absolutely ruins a program. I’d love to find a random program at whatever job I end up at and before quitting just ruin it with a random line of code that doesn’t output an error code.

    • deur@feddit.nl
      link
      fedilink
      arrow-up
      42
      arrow-down
      2
      ·
      edit-2
      10 months ago

      What the hell? Thats not funny or anything it just fucks with your ex-coworkers who probably werent the problem, management isnt affected by that.

      Pro tip, you seem really arrogant (including some other comments) and you need to tone that down before you enter the industry. Its nothing to be ashamed of and I’m not trying to insult you, you just assume your experiences are way more universally valid than they are.

    • philm@programming.dev
      link
      fedilink
      arrow-up
      28
      ·
      10 months ago

      Easy, it’s just… continue programming in python. (large codebases are a mess in python…)

      More seriously: Don’t do that, it’ll only create headaches for your fellow colleagues and will not really hit those (hard) that likely deserve this.

    • MotoAsh@lemmy.world
      link
      fedilink
      arrow-up
      20
      ·
      edit-2
      10 months ago

      Logical errors are an entire domain of programmer troubleshooting. All you’ll have to do is attempt to learn programming, and you WILL write something that throws no errors, performs terribly, and confuses you for hours.

      We all do. It’s almost a badge of honor to push past a few of them.

      Hell, sometimes it happens when no one has made an error but a particular mix of data or odd arrangement of hardware it ends up running on hits an undiscovered edge case that buggers things up.

    • stembolts@programming.dev
      link
      fedilink
      arrow-up
      12
      ·
      10 months ago

      It’s not hard to do. What would be hard would be getting it through code review. Like the example provided… how would that ever get through code review for a merge? Must not be a well-protected code base?

      • maynarkh@feddit.nl
        link
        fedilink
        arrow-up
        12
        ·
        10 months ago

        Publish your own package to PyPI that on import does some evil stuff. Name the package something similar to a known, but not too well known package. Supply chain attacks are even less defended against than other stuff.

        All this relies on companies being shit though, but well, we all know that’s the case in a lot of places.

        • MotoAsh@lemmy.world
          link
          fedilink
          arrow-up
          7
          ·
          10 months ago

          Yea… pipeline and dependency auditing isn’t trivial if you want to catch the subtle stuff. Even most of the devs that know how to do it are going to respond with, “above my pay grade…” unless they’re somehow actually getting paid enough to be arsed to do it correctly…

    • AAA@feddit.de
      link
      fedilink
      arrow-up
      8
      ·
      10 months ago

      If you’re thinking about rage quitting a job you don’t even have yet, maybe take a different career from the beginning?

      What the hell.