I’m an Economist: How Much Coding Should I know?
Whether you’re looking for a job in economics, exploring a new hypothesis, or working to publish your first paper, you might wonder: can you do this in excel? And if not, how much coding should you learn, and how will you learn it? By Kurt Semm
Five years ago, I was studying Romantic literature, and writing my sonnets. Now, I’m a Junior Economist, a Ph.D. Candidate, and comfortable coding in LaTex, Python, R, & Stata. Looking back, there were plenty of pitfalls along the way, and many of them could have been avoided with a little extra guidance.
In an attempt to spare others the struggle, I set out to determine the best rules of thumb in a recent episode of YSI’s Early Career Time.
I called in the help of three experts:
- Thomas Herndon, professor of economics at John Jay CUNY in New York. During his grad school years, he famously caught a simple excel mistake in “Growth in the Time of Debt” by Reinhart and Rogoff.
- Pier-André Bouchard St-Amant, a mathematician with a Ph.D. in economics who specializes in the analysis and optimization of public policy reforms and business practices. He teaches quantitative methods and data science at ÉNAP.
- Tim Fong, a data scientist whose Silicon Valley experience has ranged from computer vision to net worth data. He has an M.S. in statistics from Baruch College and a JD from the USF School of Law. His economic interest are in post-Keynesian price theory.
Listen to the whole conversation here, or keep reading for their 10 biggest tips.
- Don’t be intimidated. Coding just means telling computers what you want them to do. It comes down to making calculations, opening files, opening or closing loops, and creating tables or graphs.
- Don’t use excel. Government organizations might do this, but it can lead to a lot of errors. And imagine scrolling over 1,000,000 observations in a single spreadsheet.
- Choose one language to start with. Master it, and only then branch out to others. Academic economists tend to prefer Stata because it’s best for running regressions. R is helpful with cleaning Data & makes beautiful plots/graphics (ggplot2). Python is popular in the private sector.
- Stay organized. Remember to create a solid file system before you start coding, and make sure to write notes to yourself about what your code is doing. This will help your future self to replicate your work.
- Go deep. See if your school, University, or Program teaches a Computer Science Class. These often give you a more in-depth understanding than online certification courses. And the certificates don’t tend to matter that much.
- Say bye to Microsoft Word. If you’d like to get published, you’ll need to learn LaTex. It helps create nice-looking summary statistics and saves you a lot of time in the formatting stage of your research.
- Expect frustration. There will be times you’ll want to throw your laptop against the wall. Coding is frustrating because errors are inevitable. It never works the first time. Keep at it, and you’ll get through.
- Think carefully about your research question first
If you want to get through the frustration, you need to care about your research question. Don’t study a question if you don’t care about the answer. Look for something that scares you a bit.
- Remember that it’s just a tool
Any coding should be in service of your ideas, which are probably nuanced, complex, subjective, and evolving. Don’t reduce your ideas to the level of your coding skills. Improve your code to serve your ideas. - Enjoy the journey. There is a lot to learn, and many resources out there to help you. Here’s a small selection:
- Python: scikit-learn, PyCharm Edu
- STATA: Interpreting and Visualizing Regression Models Using Stata, Second Edition 2021, The Stata Forum
- R: R for Data Science (2016)
- Organizing Files: “Code and Data for the Social Sciences: A Practitioner’s Guide”
- Latex: Overleaf Tutorial
- Programming Interviews: Elements of Programming Interviews
- Coding in general: Code Complete, 2nd Edition
- Mac alternative: Raspberry Pi
πηγή :https://economicquestions.org/