"Inconsistent startups write 3.4 times more lines of code in the Discovery stage and 2.25 times more lines of code in the Efficiency stage."
This is interesting. Either inconsistent startups (startups that are more likely to fail) over-do development - or - they tackle problems that are more complex and thus require more code. The implication of the later point is that startups working on difficult problems are more likely to make mistakes (like premature scaling) and fail.
I always find there to be a very poor correlation between complexity, quality or efficiency and lines of code written. Therefore, I find the conclusion that they over-do development or approach more complex problems highly questionable. It might just be that they are not the most thoughtful programmers.
This would go along much better with inconsistency. Instead of developing software, you set your mind on scaling fast, write a bunch of code and fall into the inconsistent startup category.
I'd imagine it's due in large part to a lack of focus on the problem they're actually aiming to solve. "Even though we're solving Problem X, why don't we add Feature X, Y and Z?"
Lesson to learn? Focus on your solution to the problem people are having, and listen to your customers. Don't worry about the features you can add 3 months from now--your startup may not even last that long. Worry predominantly about getting the initial traction, sustaining it and developing a positive relationship with your customers.
Comments
"Inconsistent startups write 3.4 times more lines of code in the Discovery stage and 2.25 times more lines of code in the Efficiency stage."
This is interesting. Either inconsistent startups (startups that are more likely to fail) over-do development - or - they tackle problems that are more complex and thus require more code. The implication of the later point is that startups working on difficult problems are more likely to make mistakes (like premature scaling) and fail.
I always find there to be a very poor correlation between complexity, quality or efficiency and lines of code written. Therefore, I find the conclusion that they over-do development or approach more complex problems highly questionable. It might just be that they are not the most thoughtful programmers. This would go along much better with inconsistency. Instead of developing software, you set your mind on scaling fast, write a bunch of code and fall into the inconsistent startup category.
I'd imagine it's due in large part to a lack of focus on the problem they're actually aiming to solve. "Even though we're solving Problem X, why don't we add Feature X, Y and Z?"
Lesson to learn? Focus on your solution to the problem people are having, and listen to your customers. Don't worry about the features you can add 3 months from now--your startup may not even last that long. Worry predominantly about getting the initial traction, sustaining it and developing a positive relationship with your customers.
This stat really stood out to me.
I think it's simply because a lot of start-ups don't realize that what they are making isn't that unique.
They can leverage many components that already exist in the market.