I spent months trying to do a "perfect" Angular to React migration. Failed. Did the same with our V2. Failed again. The mental burden of carrying unshipped code for months is crushing for small teams.
Finally learned to just ship every 2 weeks no matter what. Users actually appreciated seeing progress, bugs were easier to fix, and my stress went way down.
As a founder-coder, I had the bad habit of treating every little concern and user complaints as a bug. This ended up leading to a lack of prioritization. In this article, I am going over how I classify bugs now so that I can ship meaningful features.
> While I can push back, I can’t always outright say no, unfortunately.
That sounds rough! It's extremely hard to outright say no when you are not the decision maker.
> Sometimes they go above my head
I am all too familiar with it from my days working in corporate environment. It's frustrating.
> He is the hero of the day, but maintenance has become a nightmare
100% with you there! It's like taking a loan to pay back your loan. Eventually, it's going to catch up.
Kudos to you for putting up a fight and making things to work. It's easy to follow the norm but hard to cut against the grain. Cheers to the rebel in you!
I designed my blog to enhance the reading experience and this article goes through on how I went about designing it. If you have feedback on what I can do to make it better, it would be much appreciated.
^ This and also taking a shortcut is easier. For teams that are not full-stack, doing it client-side means you don't have to bother the backend team for more APIs or wait for them to implement it fo you.
