• rumba@lemmy.zip
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    2 days ago

    I totally agree, not taking the job can mean a HUGE thing to you. It just won’t affect the company whatsoever.

    I don’t do it because I don’t like it. I worked for DOD years ago, on non-dangerous stuff but it wasn’t something I wanted to personally support.

    • m0darn@lemmy.ca
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 days ago

      It just won’t affect the company whatsoever.

      When does a company decide to recruit? It’s when current employees can’t handle the workload and/or move projects ahead on schedule.

      Not being recruited increases the hiring cycle time and means the development falls further behind schedule.

      It’s not nothing.

      • rumba@lemmy.zip
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        2 days ago

        When does a company decide to recruit?

        1. New contract
        2. Constantly to backfill

        If anyone will take the job, there is zero difference to them. Humans are not statistically morale enough to hinder them more than paying well.

        • m0darn@lemmy.ca
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 day ago

          The sooner they hire someone the less time they spend understaffed and the more they have to pay whoever the hire. It’s not a huge difference but it is also not zero.

          • rumba@lemmy.zip
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 day ago

            The sooner they hire someone The market is absolutely full of out-of-work developers. There’s no sooner right now, it’s a human smorgasboard.