 So, what motivated me to talk about giving career advice? Well, during Picon, I actually was part of the career fast and where I wasn't actually looking for a job, but I was actually promoting the company that I work for, the people that wanted to find a job. And I was finding that a lot of people, especially the new developers coming out there in the market, were having problems understanding what do they want to do in their lives, or what is it? It's like, what to expect when they become developer, right? So, after the career fair, I came with a Eureka or at least, I wish I was able to go back in time and give back the answer I had. So, a little bit of history. My first career advice came from my dad, and my dad basically told me, in life, you should take two rules, either become a lawyer or become a priest. And the only reason why he basically chose us to career pass for me is because I had this affinity to always constantly argue, and I always constantly argued and argued and argued, and I never came to an end. So, my dad said, you know what? You'd be perfect for these two parts because you'll eventually either convince them because they think you're right, or you'll convince them because you're just crazy. So, you choose which one it is. So, the next stage of the career advice I was getting is actually from schools. You know, high school where you go through career orientation, and how to figure out what you can end up studying. So, my career advice at high school was actually poor, if anything, it wasn't even what I wanted to do. So, they actually advised me to become an engineer, an engineer or an architect. So, blindly followed that, tried to become an architect, terrible. Failed, tried to become an engineer. I continued failing. Until eventually I actually fell upon a career, one of the courses that was actually programmed in C++. And that was actually the first time I actually got an A. So, voila. So, I ended up choosing computer science as a career that I wanted to do it. So, but I was also going through the university and I went through the job market and I tried to grab any job. I found out that I really, what I was being taught and what people advised me as what it is to be a programmer wasn't really what I'm seeing in the market. So, what I saw was this. I saw that the market was actually divided into three parts. You got the development that's done facing the user, you got the development that has logistics slash math and you got the development that's done facing the machine. So, if I went back and I was able to talk these kids again, I would actually look at it, I would actually explain it to them in this form. I say, well, computing or lease development is divided into three parts. So, damn, I'm running out of time. User facing, communication, find you could communicate. You understand control flow and you understand how to visually represent information. Then user facing developments what you probably want to do. And this is probably GUI development, API development and anything that kind of interacts with the user in any form. Logistics math, focus is on science, focus is on math. I mean, if you have an affinity for algorithms, if you have, I mean, if you cannot write a piece of code and feel comfortable if there's not a proof behind it, then this is the type of development that you're looking for, which is basically you're looking for development, let's say computer graphics, machine learning. Things that have dependency on concentrated, what's it called, a proven algorithm. And the third one is the machine facing. This is where understanding protocols, specifications, infrastructure. I have to give it to some people that I know here that actually could go through a specification, could read a specification document and really understand it and not die of boredom. That's, I mean, if you could go in and you could actually read and totally understand how procedures work, how, why certain protocols exist, how they interact with each other. This would be the type of position for you. This could be anything between system administrating, kernel or hardware, device drivers development in this form. So, what about Python, I mean, what can I say about Python where people ask me constantly, what can we do with it? Well, you have to understand, Python is a tool. I mean, it has its capabilities, but don't base your career on the fact that you like developing Python. Base your career on what you're capable of absorbing and what tools they use in that field.