 Hello, it's because it helps people find and fix bugs, and I think it's really important. And we found out that there were some people who used Git bisect automatically using Git bisect run, and they got really great results, hopefully I will be able to show you a slide. Yeah, no, I don't know what's going on, but yeah, there were some studies about cost of bugs, and as you know, bugs cost a lot to the economy. There was a study in 2002 that said they cost $60 billion every year to the US economy alone, and this year there was a study by Cambridge saying they cost more than $300 billion to the world economy. So I don't know if many of you have used Git bisect, but there is a command, Git bisect has many subcommands, and one of them is Git bisect run, and you can pass it a script so you can fully automate your bisection. And when you have a workflow that consists in first writing a script to that shows the bug, if the bug is there or not, and then passing it to Git bisect run, and then fixing the bug, and then committing both the test script and the bug fix together. It's a very simple workflow, but some people who used this workflow got 40% who used Git, and this workflow got 40% less bugs over one year after using Git and Git bisect, and also they got something like more than 80% reduction in time to fix a bug. So, yeah, I cannot show you some slides, but anyway, thanks for listening, and if you want the slides, I will show them on my computers.