• hesusingthespiritbomb@lemmy.world
    link
    fedilink
    arrow-up
    85
    arrow-down
    11
    ·
    10 months ago

    Changing the error level in the build config without telling everyone and then making a hyperbolic passive aggressive comic when the senior admonishes you for doing so ?

    I’m gonna guess 1 YoE, second job out of college. Enough experience to know what they’re doing, but not enough to know when to do it.

    • ThePuy@feddit.nl
      link
      fedilink
      arrow-up
      13
      arrow-down
      1
      ·
      10 months ago

      Tbh the fact that they were even ABLE to push something like that without anyone noticing is a red flag for the work environment and workflow.

    • lukas@lemmy.haigner.me
      link
      fedilink
      arrow-up
      6
      arrow-down
      1
      ·
      edit-2
      10 months ago

      I worked on software that’s roughly as bug-free as a living bug. Intended behavior crashed the software. The master branch was broken, no way to compile the software without local changes. Devs hunted down suppressed exceptions to find out why everything crashes and burns on a daily basis. Unit tests are in the backlog, we’ll get around to it eventually.

      Code reviews are ask whoever is available to approve your changes without looking at the code. Most seniors abused suppressed exceptions to use the Java Streams API, no proper technical justification. So my first official task was to unsuppress all exceptions. This caught many seniors off-guard, but made crashes infinitely easier to diagnose.

      I would’ve done that even if it wasn’t my task. Shotgun debugging is hell. I don’t want to learn which component is most likely to fail silently due to retarded suppressed exceptions. Do your job properly ffs. Don’t shoot others in the foot. Don’t shoot yourself in the foot. You have absolutely no reason to shoot people’s feet. Stop it.