Ultimately, not - it was a fun time and a learning experience. Business wise, the decision wasn't the best, I could've gone worked for more reputable companies or bigger money.I t was kind of a quick decision to join them, but it gave me a lot of experience in how to create a technical team structure from stratch/a load of shit and most importantly I learned a ton about technical debt and overcoming it. I came from a place where mostly everything was mostly organised in "standard" ways so I decided to start implementing that - starting from pull requests, workflow, CI/CD, then refactoring bits of code, teaching separation and architecture. Having to set it all up from scratch and explain why and how to do/use it to someone who doesn't know it made be research it even more so I can be sure in my knowledge when I explain it to the rest of the team. I took on responsibility and helped where I could - PM, UX, product development - that gave me access to stuff that devs usually don't get to and the responsibility paid off with more authority and trust in me.

I'd say it really depends on your situation - do you like the product? Do you like the team? Do you have stuff to learn? And most importantly, are they willing to let you take the lead instead of backstabbing you?