🚀 I share my interview with @kevinxu from @github, where he delved into the paper I co-authored with @RodrigoGrijalb1
: "Impact of the Availability of ChatGPT on Software Development: A Synthetic Difference in Differences Estimation using GitHub Data". https://t.co/OqyxdhNsOv
@ccatalini@ccatalini Thanks a lot for this paper. I use this for my Econ Modeling with LLMs
https://t.co/pzzHOVNqZN
Where students need to use @leanprover to check all the proofs and conclusions!
@noeldjohnson here is my data science course
https://t.co/cnUe4pEExK
What I asked my students is to get claude code subscription and then run all the GIS and Causal inference work in python and all the projects represent a repo in github.
@thsottiaux thanks a lot @thsottiaux ! I will present on monday my paper in @D3Harvard and I wanted this interaction to fix my math models and code.
https://t.co/cyiyarJy2P
(comments welcome!)
We measured the economics of exactly this shift 👇
When the AI stops being an app you consult and starts working alongside you, developers' frontiers expand: languages used TRIPLE at Claude Code adoption — incl. languages never touched before.
@claudeai
https://t.co/mSNuyiD1em
This is a new paradigm for interacting with Claude that is significantly more "inline" with all the other human activity org-wide. Once you do all of the under the hood engineering work to make this "just work" (e.g. across tools, integrations, compute environments, memory, security, etc.), Claude basically joins the team in a seamless way - you can talk to it as you would talk to a person and it can help with a very large variety of workloads.
Imo this is the 3rd major redesign of LLM UIUX. The first paradigm was that the LLM is a website you go to, the second was that it is an app you download to your computer. This third one is that it is a self-contained, persistent, asynchronous entity with org-wide tools and context, working alongside teams of humans. It really takes a while to wrap your head around it, but it works and it is awesome.