|
So some of what you describe is just the way of the things, but others are organizational failings. First, while "features first" may be the right mindset when in growth mode (I can't say for certain), retention matters too, and the org needs a plan to address that. Retention tends to give better ROI than acquisition, but is very easy to overlook. I worked on a product once that only focused on acquisition, not retention; that product is no more. I currently work on a mature product; I had to set draw some lines in the sand, as it were, so product didn't keep my team 100% focused on features, but instead left us room for bug fixes and tech debt. There will always be pressure to do features > all else, and organizations need to have ways of counterbalancing that. So, this is an issue that is 100% outside of you, and outside of your control, though you can advocate for it (but you are not responsible for convincing people). Second, in the comments here I saw you mention a regression. Generally speaking, regressions shouldn't happen - work to change the culture so that if a bug is fixed, a test is written. You know this is a way the app can break, you know that it has been broken this way before; it is worth asserting that it behaves correctly for future builds. This is an issue with dev culture that you can advocate for, and likely also adopt personally. Third, recognize what you can control and what you can't. Do a "good job" within the confines of the former, and learn to distance yourself from the latter. This is a purely personal issue, and will be an area to work on regardless of the job as there will always be things that 'should' be better. There is nothing wrong with wanting to feel proud of your work, of your company, etc. However, there is, pragmatically, an issue with tying your personal worth and sense of happiness to things you can't control, and it's worth working on divorcing yourself from that. Fourth, and as a counter balance to the first, work to get more business experience. You'll come to recognize that non-optimal customer experiences are sometimes the cost of doing business. Finding the right balance of what to fix is non-trivial, but ultimately with a finite amount of dev capacity, you still have to prioritize and tackle things in some kind of order. So, yes, learning to accept that that will leave things being undone for a time is worthwhile for you as well. |