I am research faculty at the Institute for Quantitative Social Science, Harvard University. I'm also a Lecturer in Quantitative International Political Economy at City, University of London and Post-Doctoral Researcher at the Fiscal Governance Centre, Hertie School of Governance. My research focuses on statistical software development and the international political economy of public financial and monetary institutions. My work has been published in peer reviewed journals including the British Journal of Political Science, Journal of Common Market Studies, Journal of Peace Research, International Studies Quarterly, Journal of European Public Policy, Review of International Political Economy, Political Science Research and Methods, and Journal of Statistical Software. I have co-authored a number of pieces on European banking union for the Bruegel Policy Contribution series. I authored a book on reproducible research methods published by Chapman and Hall. I have been a Lecturer in International Relations at Yonsei University and a Fellow in Government at the London School of Economics where in 2012 I completed a PhD in quantitative political science.
For more details, please see my CV.
Reproducibility has come a long way in political science. Many major journals now require replication materials be made available either on their websites or some service such as the Dataverse Network. Most of the top journals in political science have formally committed to reproducible research best practices by signing up to the The (DA-RT) Data Access and Research Transparency Joint Statement.This is certainly progress. But what are political scientists actually supposed to do with this new information? Data and code availability does help avoid effort duplication--researchers don't need to gather data or program statistical procedures that have already been gathered or programmed. It promotes better research habits. It definitely provides ''procedural oversight''. We would be highly suspect of results from authors that were unable or unwilling to produce their code/data.However, there are lots of problems that data/code availability requirements do not address.…