• sugar_in_your_tea@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          2 months ago

          My boss comes to me saying we must finish feature X by date Y or else.

          Me:

          We’re literally in this mess right now. Basically, product team set out some goals for the year, and we pointed out early on that feature X is going to have a ton of issues. Halfway through the year, my boss (the director) tells the product team we need to start feature X immediately or it’s going to have risk of missing the EOY goals. Product team gets all the pre-reqs finished about 2 months before EOY (our “year” ends this month), and surprise surprise, there are tons of issues and we’re likely to miss the deadline. Product team is freaking out about their bonuses, whereas I’m chuckling in the corner pointing to the multiple times we told them it’s going to have issues.

          There’s a reason you hire senior engineers, and it’s not to wave a magic wand and fix all the issues at the last minute, it’s to tell you your expectations are unreasonable. The process should be:

          1. product team lists requirements
          2. some software dev gives a reasonable estimate
          3. senior dev chuckles and doubles it
          4. director chuckles and adds 25% or so to the estimate
          5. if product team doesn’t like the estimate, return to 1
          6. we release somewhere between 3 and 4

          If you skip some of those steps, you’re going to have a bad time.

          • henfredemars@infosec.pub
            link
            fedilink
            English
            arrow-up
            0
            ·
            edit-2
            2 months ago

            In my experience, the job of a sr. revolves around expectations. Expectations of yourself, of the customer, of your bosses, of your juniors and individual contributors working with you or that you’re tasking. Managing the expectations and understanding how these things go to protect your guys and gals and trying to save management from poking out their own eyes.

            And you may actually have time to do some programming.

            • sugar_in_your_tea@sh.itjust.works
              link
              fedilink
              English
              arrow-up
              0
              ·
              2 months ago

              Yup. I actually only take a 50% workload because half of my time is spent in random meetings telling people no, or giving obscenely high estimates that essentially amount to “no.” The other half of my time is fixing problems from when they didn’t listen when I said “no.”

              Such is life I guess. But occasionally, I get to work on something new. And honestly, that’s fine, I’ve long since stopped caring about my name showing up on things.