Or they may decide to rewrite whole thing in Rust, and before that write a new framework to make sure that productivity is optimized, and write a project management tool for it first because current one sucks.
To be clear: I'm a software developer, and I feel this natural tendency too. I've gotten pretty good at suppressing it though.
Devs, especially good ones, can make good products without a PM. A PM can be a nice tool to interface with the rest of the company, Sure.
I had a PM once who listened to Dev feedback and was great at communicating with customers/users.
When done correctly priotizing features which are technically boring or seemingly unnecessary is absolutely the right way forward.
That person is also in the right position to communicate Dev effort and difficulties back.