Successfully reported this slideshow.
Your SlideShare is downloading. ×

Fail fast! approach

Ad

Fail Fast! approach
Дебажите меньше и создавайте более надежное ПО

Ad

Our target
"We should spend less time debugging code and enjoy
more time writing reliable, maintainable and beautiful code...

Ad

Fail safe! or Forgive!
Fail safe or Forgive! подход: приложение продолжает выполняться и старается
минимизировать последст...

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Upcoming SlideShare
Failfast
Failfast
Loading in …3
×

Check these out next

1 of 23 Ad
1 of 23 Ad
Advertisement

More Related Content

Advertisement

Fail fast! approach

  1. 1. Fail Fast! approach Дебажите меньше и создавайте более надежное ПО
  2. 2. Our target "We should spend less time debugging code and enjoy more time writing reliable, maintainable and beautiful code."
  3. 3. Fail safe! or Forgive! Fail safe or Forgive! подход: приложение продолжает выполняться и старается минимизировать последствия ошибки. Fail safe or Forgive! approach: the application acknowledges the error and continues execution in the best possible way
  4. 4. Fail Fast! Fail Fast! подход: приложение немедленно прекращает работу и сообщает об ошибке. The Fail fast! approach: the application stops immediately and reports an error
  5. 5. Forgive! VS Fail Fast! ● Какой из подходов лучше? ● Какой подход стоит реализовать в своем приложении?
  6. 6. Example
  7. 7. Let us insert a small bug
  8. 8. Let us insert a small bug Что должно произойти? What should happen? Что произойдет? What will happen?
  9. 9. Result
  10. 10. Let us insert new small bug
  11. 11. Let us insert a small bug Что должно произойти? What should happen? Что произойдет? What will happen?
  12. 12. Result: Panic!
  13. 13. List of software bugs, wiki
  14. 14. Case study So, what is the correct answer to the important question "What should happen?" Well, it depends on the situation. There are, however, some general rules.
  15. 15. First rule We should never "Ignore!" an error - unless there is a really good reason to do so.
  16. 16. Rule 6 of The 10 commandments for C programmers
  17. 17. Second rule is During development we should apply the Fail fast! approach.
  18. 18. Example
  19. 19. Example 2
  20. 20. Example 3
  21. 21. Third rule In critical applications the Fail safe! approach must be implemented in order to minimize damages. "Repair what you can - but when you must fail, fail noisily and as soon as possible."
  22. 22. Examples of powerful Fail fast! ● static and semantic typing, ● compile-time null-safety (no null pointer errors at run-time!), ● design by contract, ● generic type parameters, ● integrated unit testing
  23. 23. Code session

×