About code reviews and BUGS

About code reviews and BUGS

Adopting code review into the software development practice is a good way to drive high quality code, improve team communication and knowledge sharing. We'll look at the best strategies to adopt it and continue to use it in the most proficient way.

Presentation held during an #apericoder of the montacchiello.dev group.

416c04c6f0793e236381c2f5df80c9ed?s=128

Giovanni Toraldo

June 27, 2019
Tweet

Transcript

  1. 2.

    Famous software in history • 1962 - NASA Mariner 1

    mission, spacecraft destroyed ◦ 18 million USD • 1988 - Morris Worm experiment at MIT ◦ 50.000 USD • 1994 - Pentium FDIV ◦ 475 million USD • 2010 - Mt. Gox bitcoin exchange ◦ 850.000 bitcoins • 2012 - Knight Capital Group investments ◦ 440 million USD
  2. 6.

    During QA testing, receive a vague bug report, spend time

    reproducing it, write the fix and release after an hour 100 €
  3. 7.

    In production, different users spot the a bug “it just

    don’t work”, 8 hours of work 1000 €
  4. 10.

    Release to production even with many defects and missing features:

    bad user experience, loss of credibility project failure
  5. 11.
  6. 12.

    Good to have practices to the rescue • Source code

    VC • Bug tracker • Dependency Management • Configuration Management • Automated deployment • Continuous Integration • Data management • Continuous delivery • Code reviews
  7. 15.

    WHY

  8. 31.
  9. 37.
  10. 38.
  11. 39.
  12. 40.
  13. 41.