• hesusingthespiritbomb@lemmy.world
    link
    fedilink
    arrow-up
    87
    arrow-down
    12
    ·
    11 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.

    • bouh@lemmy.world
      link
      fedilink
      arrow-up
      61
      ·
      11 months ago

      It’s the delusion stage, when you think companies are places where you do professional work. Then you learn no one cares about properly doing your job. In fact, they’d rather you do not.

      • Pringles@lemm.ee
        link
        fedilink
        arrow-up
        15
        ·
        11 months ago

        Ah, that hits close to home. I have spent a lot of time and energy to get my direct bosses onboard with following best practices and doing things right from the start. To their credit, they got onboard with it and are pushing that message themselves now. Of course, the board doesn’t care about that and just jams random projects with strict deadlines without any thoughts given to the IT aspects of it up our asses, but our head of IT has apparently grown a spine and started pushing back, with some moderate success.

        The MO of my company has for years been: do a POC and then as soon as it works, push that POC in production. I’m still cleaning up the mess of idiotic shit like that from 15 years ago.

        • baltakatei@sopuli.xyz
          link
          fedilink
          arrow-up
          3
          ·
          11 months ago

          Ultimately, the quality of your work is a function of you and your resources. Corruption and miscommunication plague all management systems. Corrupt management siphons resources away from otherwise good work. Government bureaucracy is another layer of management like any other. Customers are not just consumers but working people like you.

          Hang in there.

    • ThePuy@feddit.nl
      link
      fedilink
      arrow-up
      14
      arrow-down
      1
      ·
      11 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.

    • Fedora@lemmy.haigner.me
      link
      fedilink
      arrow-up
      6
      arrow-down
      1
      ·
      edit-2
      11 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.