If the company needs a rate limiter and you don't have the budget to hire someone to create it, then maybe creating it is the sort of go-getting action we want.

If the company needs a rate limiter and you don't have the budget to hire someone to create it, then maybe creating it is the sort of go-getting action we want. And if we think the manager should go fight and persuade the organisation it needs a rate limiter then, yes. But they will need to write code to show the slowdown in latency, calculate the cost in servers if we don't have this etc etc. And frankly that sounds more valuable to the bottom line than whether Mary is being micromanaged. There are always always trade offs. "people management" is rarely about inter-personal issues arising to the level of HR like action. It is for more often enforcing standards on the job. Oh like linting. Less and less human stuff cannot be improved with coding and almost always the solution built in is insufficient, and customising it at enterprise level slow and costly. I agree don't do the job you left behind, but that's is not the same as stop coding. The software literate company will need most software not less.