#📌paradigm A risk management concept related to business practices, the organization of a [[development process]], [[the art of programming]], and sometimes human practice in general. The key idea of this approach is that if we can test something right now, we should test it right now. In a more strict version, this may imply that we should not only test what is currently possible, but also actively arrange such opportunities. When it comes to business, this means that key ideas should be tested upfront, with minimal or even no implementation. In the context of [[product management]], this implies focusing on prototypes and [[user experience]] hypotheses and putting essential specific cases first before implementing a complex and general solution. In [[software development]], this principle demands starting from the system's most fragile and uncertain pieces. Paradoxically, that implies cases where we should start from an [[API]] that contains no implementation to test our hypotheses of its usability. In other scenarios, we may need to disregard API and begin with the most complex algorithm, since our ability to implement it _is_ the problem. The essence of the fail fast approach is to identify and to take the greatest risks immediately. The reasoning is simple. Some risks are essentially unavoidable. The longer we postpone facing them - the more time and effort could be wasted. --- <font style="color: #F86759">Contributors:</font> *[[Mykhailo]]* <font style="color: #F86759">Last edited:</font> *2024-03-27*