If you are putting your energetic resource in a way not requested or required by the project, then you are wasting it. Or your incentives are not aligned or properly communicated.
How many times in commercial software, do you put all your heart into a thing and it gets promptly thrown into the garbage? All the time, in my experience.
Do what's barely good enough, and reasonably maintainable, and always focus on how your efforts translate into business income. That's a new definition of perfectionism that is universally valued.
I feel like I am extremely empathetic towards other engineer, as well as customers. I hate slow and buggy software as an end user. I don’t want other people to have to deal with it.
I also don’t want teammates to have to do things they aren’t good at, or interested in. A backend dev should not need to learn the many intricacies of InnoDB tuning; they just want the ORM to talk nicely to the DB. I on the other hand absolutely love tweaking low-level things like that. So far, the devs have also expressed joy and gratitude that I enjoy this stuff. I have to assume customers enjoy reduced latency.
So anyway, no, don’t focus purely on revenue. Focus on making people’s jobs easier and more pleasant, and on making customers happy. Revenue follows.
Disclaimer, not a business person nor any interest in it whatsoever.
If you are putting your energetic resource in a way not requested or required by the project, then you are wasting it. Or your incentives are not aligned or properly communicated.
How many times in commercial software, do you put all your heart into a thing and it gets promptly thrown into the garbage? All the time, in my experience.
Do what's barely good enough, and reasonably maintainable, and always focus on how your efforts translate into business income. That's a new definition of perfectionism that is universally valued.