• bleistift2
    link
    fedilink
    English
    arrow-up
    62
    ·
    5 months ago

    In my experience it’s the other way around.

    • Potatos_are_not_friends@lemmy.world
      link
      fedilink
      arrow-up
      47
      arrow-down
      1
      ·
      5 months ago

      Both sides.

      I constantly call out juniors who do things like ignore warnings, completely unaware that the warning is going to cause serious tech debt in a few months.

      But Ive also unfortunately shrugged after seeing hundreds of warnings because to update this requires me to go through 3 layers of departments and we’re still waiting on these six other blockers.

      Pick and choose I guess.

      • bitchkat@lemmy.world
        link
        fedilink
        English
        arrow-up
        9
        ·
        5 months ago

        Then things will have to wait until the code is of sufficient quality to be accepted.

    • gravitas_deficiency@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      4 months ago

      Yeah I’m one of the “I only want to write this fucker once so I will make it as solid as I can” types… and my manager/team-lead/principal dev (all the same person - that’s a whole other story) is the “yolo send it” type.

      We do not get on well. I’m probably going to switch teams or jobs soon.