• 3 Posts
  • 378 Comments
Joined 3 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.




  • Of course projects will have a bigger ROI if the infrastructure is effective and industry built up in the area meaning it’ll effect more people. People won’t eat in a restaurant with no windows, broken tables and dirty forks. By only investing in high ROI areas you increase risks of all the economy being hyper focussed in one area and admit you have no idea how to economically develop an area. You also cannot ignore decades of underinvestment and only focus on recent investments. The goal is to activate and connect other economic centres like Leeds and develop new ones. If you have places like Newcastle, Liverpool, Hull connected, you stem the brain drain and allow people to commute or even companies to invest because it won’t take 10 years to get to London to work with other companies.

    By your posting I can tell you’ve never spent much time up north or commuted by the rail network and as a result, you’re focussed on the information that backs up your world view rather than developing an economic view that is holistic and brings everyone with it rather than further enriches the 12m people in Greater London. Also you discount that if the economy was better developed up north, less outgoings would be on welfare giving more opportunities for a more generous tax regime for companies and the benefits that could bring.

    No everything is covered by narrow metrics like ROI, and we haven’t even covered ethical considerations like the fact the government has a responsibility to all the electorate and everyone deserves to benefit from good infrastructure. The country got rich on good industry and that wealth ended up invested in the south as the economy moved from industry to services based.



  • You’re trusting a PO to decide on how you build? They ain’t coders. They decide on value, you estimate and build and they prioritise based on the information you provide. POs aren’t the boss of devs. That’s usually engineering managers. You are both specialists in your field. You don’t lecture them on value and how pointless a feature is, you size it, and using velocity they can anticipate how much will likely be delivered in next sprint. If they really object, “if you feel you can build it in 1 day, go ahead, ill give you access. I have no idea how that could be done”

    PO wouldn’t like it during live incident when shit goes wrong that you suggest “I did highlight the risk of this occurring and proposed mitigation steps but was overruled”.


  • “True. It’ll be perfectly fine, and because of that, you won’t need me on call when it all goes dramatically wrong. If you need access to the repo, I’ll add you in though. Good luck.”

    Or, if you’ve worked together a while “like I overthought it when we worked on x, and y went wrong, and I called it before it happened. Turns out I’m quite good at seeing car crashes in advance.”


  • Mad? In a professional workplace?

    “If you can give me that issue free codebase, I’m happy to do that, but failing that, it takes 3 days to add that feature that is akin to the leaning tower of Piza taped together with duct tape. There is only so much tech debt you can pile on until you are in code hell, and unfortunately, we are.”

    If they do some weird ass schedule “well, you can write down that if you wish, feel free to write down that my other car is a Bugatti, if we are just theorising on a perfect unicorn world”.


  • “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”.


  • That ain’t pretty. In the UK, there is much more trust and less micromanagement, though it’s important devs learn to be assertive, communicate well and don’t give too much info to be hanged with. The way you communicate can determine his much time you free for yourself. A baker never asks of they can use flour and egg or negotiate on cook time.

    Context is important though and if folk find themselves in the cheapest price consultancy, they probably need to find their way out for their own self-respect and mental health. When you find your way into an org that wants to build quality stuff, it’s much happier for them.