3 ms·
There's no moral/ethical/character shortcoming/failure/flaw here. The company has leveraged technical debt. The leverage has allowed the company to grow. The d
by brudgers 10y ago
There's no moral/ethical/character shortcoming/failure/flaw here.
The company has leveraged technical debt. The leverage has allowed the company to grow. The debt increases the likelihood of bugs. Technical debt is a business decision. It's use is a sign of technical competence, not incompetence.
Customers complaining is better than not having any customers. The business goal is not some bug free codebase.
My random advice from the internet:
1. Accept technical debt for what it is. A business tool.
2. Talk to the customers. If stability matters more than
new features, focus on stability.
3. If stability isn't your customer's overwhelming priority,
keep moving forward iterating on their feedback.
What you are doing is hard. The good news is that there aren't grades every three months. It's a marathon not a sprint.
For a startup, technical debt will tend to disappear in one of two ways: the startup shutters its doors or the startup grows to a scale where even original systems with zero technical debt would have to be redesigned. Then you have to build Kafka or Kubernetes or Wasabi.
Good luck.
- Devdealer 10y agoThanks brudgers, I appreciate your input. I think there is some truth in what you've said. However in my case it wasn't a conscious choice, in fact my conscious choice at many points along the way was to improve quality, stability, reduce bugs that make to production etc. And I haven't done it. So I cannot claim quick and dirty was as strategy. I would have been ok with that for the first 6 months but we are past that. I want to face up to the fact that I need to change. Also I have a suspicion that doing things well becomes faster and more efficient than quick and dirty quite quickly. Thanks for your words on encouragement.
- brudgers 10y agoI am curious what the business case is for the intended change. It seems to be missing from the described context.