[–] 12 points 4 months ago

I was in this story in a past life. I've been most of the engineering roles it feels. Luigi is the worst one to be stuck in.

After this job, Luigi tried to get out of the oven business but in every interview after this, "oh you've worked on ovens? Nice, we have a few oven problems to solve here. "

  • source
  • [–] 16 points 4 months ago (3 children)

    I don't work in programming (helicopter maintenance/repair), but my boss goes one step further.

    Boss: How long until it's ready for a test flight?

    Me: I'd say...

    Boss: Wait. Give me an honest number, don't add buffer time. I'm already going to double whatever you say to tell District.

    Me: Oh, okay, with paperwork and ops checks, 3 hours is feasible, as long as we don't encounter any other issues.

    Boss: roger, six hours, sounds good.

  • source
  • parent
  • context
  • [–] 23 points 4 months ago (4 children)

    I’m really sorry this seems to be so common. I’m in a position where my PM accepts the team’s estimate, and even understands it’s just an estimate.

  • source
  • [–] 19 points 4 months ago* (last edited 4 months ago) (1 child)

    Usually:

    Manager: We (meaning you) need to do task A. How long will it take?

    Me: Task A will take X days to do.

    Manager: That seems awful long, are you sure you are using our choice of AI tool correctly? NVM I vibe code that myself

    Later:

    Manager: Here is my vibe coded single PR with features A, B, F, and some refactoring. I have no idea what it does, could you check that it works? I have no specs, documentation or tickets for any of this and I don't have time to fix failing CI gates

  • source
  • [–] 5 points 4 months ago

    I usually tell them that I need to do it to in order to estimate how long it will take next time. next time it will already be done, here it is.

  • source
  • [–] 13 points 4 months ago* (3 children)

    Oh nice one.

    You can also add another layer by adding "you know that [infrastructure requirement] from [notoriously uncooperative infrastructure team] is gonna take at least Z days right?", and if it isn't enough, go for the kill shot "I'm gonna start writing the architecture principles this sprint, getting back to you as soon as they are cleared by [notoriously picky and detail obsessive software architect].".

  • source
  • parent
  • context
  • [–] 120 points 4 months ago (6 children)

    Fun fact, you can play tough too.

    Manager: We (meaning you) need to do task A. How long will it take?

    Me: Task A will take X days to do.

    Manager: That seems awful long.

    Me: How long do you think it should take?

    Manager: It surely could not take any longer than Y days.

    Me: Ok, which features are you willing to remove to make it fit in this timeframe?

    It's surprisingly effective, especially with a bit of seniority.

  • source
  • view more: ‹ prev next ›