This blog post is authored by Brandon Rohrer, Senior Data Scientist at Microsoft.
I gave a webinar last month titled “Data Science for the Rest of Us”. Thank you to all of you who joined me live and many others who caught the recording online. If you can think of someone else who might enjoy it, please send the link their way.
I got a lot of excellent questions from you, but the most popular by far was “How do I become a data scientist?” I looked online for an answer I would feel comfortable sharing with you all, but I didn’t find one. Instead I found checklists. There were lists of computer languages to study, software tools to get, technical skills to master, communication techniques to practice, online courses to take, online communities to follow, universities to attend. The lists were thoughtfully written by excellent data scientists, but I didn’t find them helpful. If I had come across these when I set out to become a data scientist, I would have been overwhelmed and a bit discouraged. And I was mildly troubled that I haven’t completed a single one of them.
After giving the question some thought, here is the answer I would give my own children:
Being a data scientist is like being an athlete or a cook. An athlete is someone who does sports. A cook is someone who makes food. A data scientist is someone who builds things using data. No one has to give you permission. Choose a tiny project today and jump in. Plot the heights of all your houseplants. Predict your commute time using the weather. Estimate the probability that your team will win the Super Bowl. It doesn’t matter what you pick. It doesn’t matter if you do it wrong. It doesn’t matter if the results are pretty. Just make something.
Don’t worry if you don’t know how to do every part your project. In fact, it’s best if you choose something you don’t know how to do. If you decide to write a mobile app that recommends the best local brewery based on your location, don’t worry that you’ve never written a mobile app or tried a craft beer. Just get your hands dirty, do the research, and learn what you need to know. If your project needs it, don’t be afraid to learn a new language or a machine learning algorithm. Or even to write your own. And don’t worry about learning it in a traditional or classroom sense. Learn just what you need, just well enough to build what you’re making. Your project will tell you what you need to learn next.
Build something you can point to and feel a swell of pride—a picture or a demonstration or an app or a set of files on GitHub or a Word document—something you could show to your mom (or an interviewer) and say “Look what I did!” And when you finish it, turn around, pick another project and start over again.
Building things is the way I became a data scientist. I built lots of small projects as part of graduate school courses, professional research programs and hobby work. My favorite project is a long-running moonshot at general purpose artificial intelligence for robots. It still doesn’t work as well as I’d like, but in the process of working on it over the last 15 years, I’ve learned python, created my own on-line deep learning and reinforcement learning algorithms, written a physics simulator, rendered my own videos, and a hundred other things that, now that I think about it, look a lot like a list.
Building things is one of the great pleasures in my life. I hope you enjoy it too.