Comment by ramon156
5 days ago
My first job was the only job I just went home from and just cried because of how useless thah job felt. We were building a SaaS that took weeks for a simple update with 8 devs (of which 2 were actually good).
This was purely because of the legacy stack and poor management. The boss wanted to scale but did not care about tech, so we just never made real improvements. Sure, a feature got implement at least a week. We saw revenue grow a ton. We never saw time to improve our stack.
Safe to say I felt like I was adding nothing to that company. They just didn't want to grow despite saying the opposite. I get that the shiniest framework will not improve the project, but there were some serious bottlenecks that just got shoved under the rug
I'm a bit confused by your post here.
> The boss wanted to scale but did not care about tech... We saw revenue grow a ton.
Sounds like the boss was largely getting the scaling they wanted?
Every situation is different and there are people with way more experience than me here, but in general terms I've seen the "we need to rewrite / write a component library" from immature tech. Problem is, they're never satifised, so after they're happy and they've moved on, the next person will say the exact same thing.
That's not to say your code didn't have real problems.
But experience tells me that there's tons of well written projects with no users or revenue, and lots of broken shit making money hand over fist. All else being equal, unless you're in a bubble, you're better off with the money.
( Not intended to imply the job wasn't terrible and the product didn't have real actual scaling problems making your life terrible, I've seen that too ).