

Carolina Celis-Laverde
253 posts

@ccelislaverde
Research Fellow @the_IDB. BA, MA Econ @EconomiaUAndes. Macro, monetary economics, and heterogeneity.





most of the junior econ faculty I talk to are finding somewhere between "less" and "almost no" use for research assistants for simple tasks - data cleaning, making tables, running regressions - in the time it would take them to give instructions to the RA, they can instead just instruct CC and get the results (and done much better) so, the potential utility of an RA often depends now on the RA having high quality higher-level/architectural thoughts, being skilled at interpreting and iterating on the results of code, and/or being better at using coding agents than their prof yes, ofc RAs may have a comparative advantage despite not having an absolute advantage - but this is quite tricky a lot of the difference between mediocre and great results with agentic coding depends on having a simultaneous good mental model of the tools, how to work symbiotically with them, *AND* of the architecture of what it is you want to do (whether software or research) in the past, an RA would work slow enough - because the process of writing code was slow, so that you - as a prof - could catch them in all these small problems/mistakes they'd make along the way due to a lack of experience even so, reviewing RAs code was already a bottleneck for many profs now reviewing (tens of) thousands of lines of vibe coded RA code, esp if poorly thought out, is just untenable worth saying - the pool of junior faculty I talk to are highly selected, bc they're either coming to me for agentic coding training, or they're my friends and so have had to listen to me blather on about this stuff for the last year I do expect though that the sentiments of these junior faculty is wider spread than is implied by what economists are publicly saying about "RA replacement", because it's an unpopular/costly opinion to publicly voice that you don't need your RAs anymore

























