Hi, I'm Evan. I'm a learning portfolio manager here at Google. I don't think I'm a computer science or super engineering type, but I really, really like working with numbers, so actually, I went into accounting. And about after two years of accounting I said, "Wow, I really don't want to do all this by hand," so I took my first information systems class, where they taught me the language SQL or S-Q-L, and it completely opened up my mind. Between a working knowledge of spreadsheets where you change one cell and the whole spreadsheet changes because those amazing calculated fields and SQL where I can query billions of rows of data in a matter of second, I was completely sold on my love for data. I've dedicated my life and my career to just communicating that passion and getting folks excited about the things that they can do with their data. Why is SQL such an amazing first language to pick up? Well, there's so many things that you can do with it. I will first caveat and say, I am not a computer science major. I don't know deep down Java and Python, and I was a little bit apprehensive of learning a computer language. It's like a pseudo-programming language, but in reality, you can write your first SQL statement as you're going to find out here in just five minutes or less. SQL, honestly, it's one of those languages that's easy to learn and even more fun to master. I've been learning SQL for 15 years. I've been teaching it for 10. As you're going to see in some of these hands-on labs you'll be working through, it's very easy to return data from within a database or a data set. Just select whatever columns from whichever database that you're pulling from, and immediately you get the data back. Now, the really fun part is actually teasing apart and saying, I wonder if I change my query, add these more columns, filter this data set a different way, share with my colleagues. It's meant to be an interactive querying language, and "query" means "asking a question." If I can challenge you one thing, it's that the syntax for picking up SQL, much like the rules of a chess game, are very easy to pick up. But the hard part is actually not the syntax writing, much like with any programming language, but the actual what question do you want to ask of your data? What I would encourage you to do is be super curious about whatever data set that you're given. Spend a lot of time, even before you touch your keyboard, in thinking about what data set or what insights you can get from your data. And then start having fun. There's many different ways to write the same correct SQL statement, so try one out, share it with your friends and then start returning that data back for insights. Good luck.