What Developers and Economists Can Learn from Each Other!
summary
Claims that hinge on missing controls and an Excel copy‑paste error turn into concrete fixes: add unit tests integration and regression tests, use version control on GitHub, and prefer standard libraries over black‑box executables. Examples include a high‑profile debt‑growth overstatement and other papers whose effects drop to near zero after code fixes. Practical tools discussed: Python and Julia libraries (quant‑econ project), GPUs for linear algebra, memoization and dynamic programming for nested loops.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:44This isn't an econ conference!
- 4:48Coding Gets Short Shrift
- 6:20But There's Hope!
- 9:16You've got results!
- 9:58Disasters in Econ Research
- 12:44Modeling in One Slide
- 13:26Troubleshooting Like an Economist
- 16:34Comparative Advantage!
- 18:02A Premium on the "Hardcore"
- 18:42Only as Good as What We Tolerate
- 20:01What Can We Do?
related talks
45mA Teacher, an Economist and a Developer Walk into a Bar...
50mExpert Software Developers' Approach to Error
48mA Teacher, an Economist and a Developer Walk Into a Bar
51mYour worth as a developer: not what you do, but why
19mLearning from eight years of data science mistakes
01h 24mKeynote: Optimizing for Change
30mLessons Learned: A Developer's Perspective on Teaching & Learning
51mA Teacher, an Economist and a Developer Walk Into a Bar