Skip to 0 minutes and 9 secondswhat can you tell us about bugs? Okay, so there's the story. In 1947 a group of technicians at Harvard University were running their electromechanical computer and they noticed a lot of errors. So they opened up the computer and they found a moth. They found an actual bug! So they dropped the logbook, took the moth, pasted it in and wrote the following
Skip to 0 minutes and 38 secondswords: "first actual case of a bug being found". And from that day onward we've been using the word bug to refer to glitches and flaws in any system. So why are bugs bad? Seriously? Besides making your life as a programmer miserable, they can have really dramatic consequences. In 1996 the launch of an Ariane 5 rocket failed due to a bug in the inertial reference system. 40 seconds after launch the rocket exploded ... Just like with real bugs you want to prevent an infestation. So, it's crucial that you adopt a defensive programming style to reduce the number of bugs in your code. In this MOOC will discuss professional tools and advanced techniques for debugging serial and parallel programs.
Skip to 1 minute and 30 secondsSo, you'll minimize the time and frustration spent on finding and fixing them.
Skip to 1 minute and 35 secondsWelcome to our MOOC: "Defensive programming and debugging"