2 ms·
> you don’t know of all the failed projects that couldn’t get off the ground because of incompetent development team and practices that lead a product to its de
by aiisjustanif 3mo ago
> you don’t know of all the failed projects that couldn’t get off the ground because of incompetent development team and practices that lead a product to its demise
Trying to ignore the nuance is hard in your position or the following one I’ll give is difficult.. but is the opposite potentially true as well? We don’t know how many projects failed because of over optimizing, too much time spent on design and engineering decisions. It’s of getting out and MVP to market. I only say this because I have been apart of a few of these.
- bsenftner 3mo agoWell, that's the other side of incompetence: they know how to spin their tools, but they don't know when to stop, or how to stop the change requests, the balance between shippable, maintainable, and what the market wants at that time.
- hatefulheart 3mo agoI understand and of course I am familiar with the hypothetical you are trying to set up here but I was specifically pointing out a logical fallacy I see banded round all the time by people who should know better or educate themselves. I will say that if “good engineering practices” comes up in your root cause analysis for a failure to launch a product you are not thinking critically.
- resonious 3mo agoOver optimizing and spending too much time on engineering decisions is also something an incompetent development team would do.