• 0 Posts
  • 7 Comments
Joined 2 years ago
cake
Cake day: August 5th, 2023

help-circle


  • Delayed response, but raise a ticket in retros saying retros should be cancelled. Andvwhrn asked why, say nothing is followed upon or learn so there is no point doing them.

    Then you can talk shit about them and make clear without change, you won’t commit time to next one as there is no point.

    Could be fun to see what the response is.


  • “Why are we only learning about this now? How long has this requirement been known? I think we need to look into the process that work comes into the team otherwise, if we don’t learn, we are going to take the website down and cost the company thousands/millions. It’s worth working with the business to get a batter understanding of upcoming requirements so we know what’s going to be needed in a months time”. There is a reason retros exist. Oh, and you have to be good at teasing out real deadlines vs arbitrary deadlines made up with no justifiable reason.

    “You ask me how long it’ll take, and it’s 3 days. You probably need to manage expectations on this. Maybe let them know the risks of x, y and z and why it will take this long”.



  • This why any good engineer would bake it into their estimates when working around the area. I think Martin Fowler covers this in Refactoring. Eiher that or it was Kent Beck in TDD. Both books complement each other really well.

    A good civil engineer doesn’t ask a Project Manager if they can add in structural supports. A good software engineer shouldn’t ask to build things right.

    “Before we build x, we need to adapt the foundations by resolving x problem. If we don’t get this right, it’ll increase the chances of bugs surfacing in production and would make our team look like a joke.”