> If all you were doing is taking requirements from someone else and poorly coding them up

So, in your entire career, you've always worked in companies where you were a subject matter expert on everything the company did? Always knew the business domain inside out? You were running the numbers, sitting with customers, and determining yourself what they really wanted?

> If you push back on requirements when they are not reasonable. Etc

I did, because the requirements had a cost, which I had to balance with limited resources.

If widget A would make 10 customers happy, but would cost two weeks of work, that could be better spent making widget B that'd make 20 customers happy, then it would not be reasonable.

If widget A and B are free, then it becomes unreasonable to say no.