Code quality and hand-over process when getting acquired

Cross that bridge if/when you get there...

I've been in a company that acquired a terrible spaghetti code base for millions. They didnt want the code, they wanted the data and user base. Big companies will do their due diligence before acquiring but as long as buying doesn't put their company in a compromising position (security, leaks etc) the code probably wont matter. Just focus on building

Seems like something you don't really need to optimize for. It's hard enough just to make a business work. Even less chance that it will get acquired.

But I will say that it would probably benefit you if you spent time on learning how to write better code. You will like to code better when you have to change old code and it will make you faster in the long run.

Code quality is generally of no consequence during acquisition.

I also think it won't matter too much. However, to name variables and split the code into functions, you don't need a CS degree. If I were you, I would focus on improving code quality whenever you add something new to the codebase. Then at least new parts of the code are clean.

Railax ,

" my code sometimes tends to be quite spaghetti-ish, variables have not the most adequate names and my folder structure isn't the most logic in the world. "

The code is the only real asset you have for an app/website .

If you were buying a car..and looked under the hood..and saw spaghetti-ish wiring on the engine...would that inspire confidence in your purchase ?

Fix the bridge before you have to travel over it ...in the car .

Thank you so much guys!