Once my business is in a more profitable place I’ll bring someone on to fix up the code
AKA: technical debt. I actually approve of this approach when you’re testing the market and don’t have any paying customers. Where it gets ugly is when customers start placing trust in your product, trust that might be costly if your code fails, and management doesn’t budget the resources to actually fix up the code. I was very glad to leave the place that was doing this…
The tools I’m using are for internal use and there is a backup in place. So, if something does go down, my contractors can pull the files up in one drive in a view only format.
AKA: technical debt. I actually approve of this approach when you’re testing the market and don’t have any paying customers. Where it gets ugly is when customers start placing trust in your product, trust that might be costly if your code fails, and management doesn’t budget the resources to actually fix up the code. I was very glad to leave the place that was doing this…
The tools I’m using are for internal use and there is a backup in place. So, if something does go down, my contractors can pull the files up in one drive in a view only format.