6 ms·

You might be right about the ultimate outcome, but I think the questions you ask may be wrong. In the example of changing the checkout to React I might ask myse

You might be right about the ultimate outcome, but I think the questions you ask may be wrong. In the example of changing the checkout to React I might ask myself would it increase development trajectory and look for numbers related to that. Things like how many features were delivered last quarter and what was the scope size of those features? How might these things fit into a react framework and does it improve delivery times on our future project plans? Is our system a proprietary one and how long would it take to onboard a new developer vs hiring someone that knows React and can add value within a week? It's easy to decipher that nothing is wrong with the checkout page as it exists from performance. What's really being proposed here is an attempt to get ahead of it before it becomes a problem. Keeping the growth needs of an engineering team in mind you have to remember nobody wants to work on a technical stack that uses ancient technology and hasn't been updated because "it's not broken". The evaluation just seems like it's too narrow of a focus the way it's worded here. Just my 2 cents though.

asmithmd1 4y ago
but I think the questions you ask may be wrong Exactly this. You asked one question that you summarized dismissively as "...because they had read a blog post about another company doing it." You could have stroked their ego a little by saying that you don't have the breadth of perspective that they do, before asking questions about what they perceive as the advantages of switching to React. Would it help get the team more visibility or credibility? Would it help advance their work goals? What they should have asked you is: How long will it take to switch? What is your technical opinion of making a switch? They are not asking for push back about what concrete problems need to be solved. There are infinite ways to implement a solution, for some reason a manager focused on this way to create a solution, they want to know how long it will take and if you are interested in doing it, or would hate doing it.

asmithmd1 4y ago

but I think the questions you ask may be wrong Exactly this. You asked one question that you summarized dismissively as "...because they had read a blog post about another company doing it." You could have stroked their ego a little by saying that you don't have the breadth of perspective that they do, before asking questions about what they perceive as the advantages of switching to React. Would it help get the team more visibility or credibility? Would it help advance their work goals? What they should have asked you is: How long will it take to switch? What is your technical opinion of making a switch? They are not asking for push back about what concrete problems need to be solved. There are infinite ways to implement a solution, for some reason a manager focused on this way to create a solution, they want to know how long it will take and if you are interested in doing it, or would hate doing it.