I always tell my students the way you make your project shoot to the moon is by writing it in Jupiter. Professional people with PhDs on a mission to make great discoveries. Use an IDE called Jupiter, like they're doing a school assignment. Where is the Zant of Python? Yes, we use the notebooks for our students, but not for our production code. I mean, for production code, we also don't use Python. Or do we imagine somebody accidentally writes a SkyNet in a Jupiter notebook? A Jupiter debugging in a spider, I-Python. Jupiter is a pain, a pain. Of course, we only do our research in Python. Our prediction model is then running in C. Back in the years, I thought AI was scary. Data science required a PhD, and computer vision was magic. Now it's all just five lines of code in Python. Were companies used for data science? All of them. Nobody likes smart lab or R or SAS. Let's not mention Julia. No, no, no, this is not for recording. Intel, IBM, JP Morgan, Goldman Sachs, Spotify. They all use Python in-house to predict trends of in-house coffee usage. What can I say? Automation, innovation, revolutionary, pain. We don't use Jupiter. No, well, sometimes you've got to show how your code works. Now I sound like a PhD, but don't worry. I'm only a data scientist for quantum physics operations. First, import numpy, then import a rest. Carousel in-house, and we create a sky-net. I always get confused when switching between MATLAB and Python. A one starts with a zero, and one is a zero.