News for hackers. Stuff that matters.

throwaway2FA69

Thanks, I think this is good advice. Planning to do something around those lines.
Yes, I think you make a good point about the deadline. It's an internal deadline, but I do feel like this team was formed to build this particular feature, so missing it would be a big fail.

Based on that, I feel like the blame won't be on the TL, which is what worries me, but that's probably unfunded/unfair.

fwiw, I don't think they're incompetent! it was a ~4 month project that's due in two weeks now

what doesn't make sense about your last theory, why don't chime in when the multiple specs/documents where defined? why now?

After thinking this through with the answers in here, my current guess is that this is something that just occurred to them, which is totally fine and I shouldn't be frustrated about it, these things happen.

thanks! appreciate the response. I do think they probably have valid concerns, and I absolutely trust them.

The frustrating part for me is why wait till the last possible minute? why avoid talking about this until it's too late? I would have loved to have the chance to design it better upfront, or at least have a conversation about it.

It's possible they're overwhelmed with work, it's also possible that I'm making the deadline a bigger deal than it should be.

Your response was super helpful to think about this, thank you.

Ask HN: How to deal with last-minute changes by team lead derailing deadlines?

- We have a hard deadline for a feature.- Early attempts to define the API were repeatedly dismissed ("too soon").- Team proactively built API proposals (with docs, examples, OpenAPI spec).- Two weeks before deadline, TL finally agreed to our approach.- Two PRs in, while reviewing the final PR, TL changed their mind entirely. Wants to change the approach but is unable to express exactly what...

( Read More... | 12 comments | on HN )