4 ms·
But the success is not directly inherited from technical debt. Technical debt bought time that enabled the success to happen (maybe before the company ran out o
by crdb 10y ago
But the success is not directly inherited from technical debt. Technical debt bought time that enabled the success to happen (maybe before the company ran out of money, or allowing it to launch months ahead of the competition), but the company would not have failed if you somehow built it "properly" and otherwise met those constraints.
In other words, you can rationally make the decision to take on technical debt if it allows you to meet those constraints. It isn't a black and white decision.
It seems obvious to say this, but I know plenty of founders and investors who have had success (survivorship bias - if they hadn't they wouldn't be investors/founders) with the technical-debt-and-grow method and therefore apply it to every problem.
- taeric 10y agoAny way you formulate this, it is entirely possible that taking on technical debt is required for a largely unbounded success. It may be a couple of steps removed, but it is still a direct line. Time to market is a vital metric for everyone. Anything that can help hit a tight time to market can add to the success of a company. Can you reformulate it so that time to market was irrelevant for success? Only if you are comfortable with what is likely a bad model.
- crdb 10y ago> it is entirely possible taking on technical debt is required for a largely unbounded success > Time to market is a vital metric for everyone I disagree with the first statement (I know plenty of exceptions, enough to statistically consider that it is false) and disagree with what you imply with the second. Google launched against 5-6 strong, established search companies. Copying the then-strategy of paid listings was not going to work, and their technology had to be ready before hitting the market. Theranos is an example where the technical debt did not pay off. Time to market was not as important as getting the tech to work. I had a long meeting/debrief yesterday with a C-level from a freshly failed, large internet group. Their CEO and CTO's strategy to get out of the hole was to technical-debt-and-grow a dozen products in parallel in the hope one sticked; whilst several stuck, they did not have the expertise or willingness to do the work to stop the products from breaking, and the company failed by running out of money (which, due to technical debt stopping the accountants from having any visibility, surprised them all). I consider their failure to be entirely due to the idea that technical debt is required for a large unbounded success, which was like a religion for the CEO and CTO. Had they gone "private equity" (cut headcount, focus on core business, invest time in cleaning up) they might have survived long enough to become profitable again. Many business founders will not have the resources (reputation, money, or even just hustle, EQ and maturity and leadership) to get a good technical co-founder and will have to either take shortcuts, or reconsider their decision to start up without said resources.
- simula67 10y agoI wish this was true, but we can see that it is not. Take a look at successful programming languages. Languages like PHP, Javascript are hugely successful, despite universally acknowledged to be terribly designed. In open source world, despite having very poor reputation for code quality, projects like Wordpress, MySQL are more successful over supposedly well written projects like Postgres. One exception to the rule is Perl, which lost out to Python as the de facto scripting language over time ( Python is supposedly better designed that Perl 5 ). But these are exceptions, not the rule.
- taeric 10y agoYou are shifting my claim from it being a possibly necessary criteria, to it being the sole criteria. Worse, you are shifting my claim to be that technical debt somehow guarantees success. Neither of these are my assertion. I simply assert that time to market is a vital metric. If hitting a vital time to market means making some tradeoffs (what we now call technical debt) then, so be it. Take your examples, do you really think that Google did not make some tradeoffs? Having seen some of their products (I'm looking squarely at the pieces of crap that were my early phones from them...), I can confidently say they make rash decisions all of the time. Now, there is a silly double speak that we have in the industry where we say "technical debt" when we really mean just poor work. There is a lot of conflation in the world where these two should not be mixed.