>do I need to give this to someone else

Could mean "I didn't know you had so much stuff on your plate that takes precedence". You're giving 0 benefit of doubt to a PM who in my opinion was right to push back because for a non-technical person it's not easy to grasp why drag and drop should be so much harder than other similar impact features.

> to a PM who in my opinion was right to push back because for a non-technical person...

Ah and there's the rub. A PM in a software project should not be a non-technical person (because tbh what's even the point, how would a 'non-technical' person even be able to evaluate technical decisions and their implementation?)

Would you fly in a plane, or drive over a bridge that was built under supervision of a 'non-technical' PM?

PM has to be nontechnical so they can manage the symptoms. PM also has to be technical to not trigger the worst of

Or, they can simply be better at management.

The head of a space program doesn't need to be an astronaut. An admiral doesn't have to know how to swim. A PM doesn't have to know all the various engineering disciplines the project may touch.

The comment was derisive, and therefore poor leadership. Period.

You could be right. Depends on their tone and previous interactions. This is why it is good to have rituals and processes where e.g. you estimate a bunch of stuff at once and it is clear what kind of estimate it is. Effort, elapsed time or Tony's elapsed time given he is going to a conference Tue to Thu.