No.
OK, so, you optimize a piece of code that doesn't need it. Let's say that code develops a problem that someone needs to go in and fix. Because of your optimizations, the code is now harder to read and the bug takes longer to fix thus costing the team time and money. Time and money that was essentially tossed into a bucket and burned because someone decided to optimize a piece of code that didn't need it.
Now ... who's the unprofessional one in this situation? The optimizer who believed that optimization is never the wrong choice.
OK, so, you optimize a piece of code that doesn't need it. Let's say that code develops a problem that someone needs to go in and fix. Because of your optimizations, the code is now harder to read and the bug takes longer to fix thus costing the team time and money. Time and money that was essentially tossed into a bucket and burned because someone decided to optimize a piece of code that didn't need it.
Now ... who's the unprofessional one in this situation? The optimizer who believed that optimization is never the wrong choice.