← All topics

ai uplift

1 capture, most recent first.

Thariq @trq212

Thariq @trq212 · Jan 21 This was a legacy migration, we had to port our entire rendering engine while making sure nothing user-facing broke. Doing this without Claude Code could have taken on the order of 1-2 years for a single engineer, something we would have never been able to prioritize. [17 replies, 13 reposts, 212 likes, 160K views] Thariq @trq212 · Jan 21 Wanted to clarify this 1-2 years thing. Of course this was just a back of the envelope estimate, it's entirely possible it's wrong. And Claude Code itself is like a year old, so how could this take longer? As a team and company grows, your codebase moves under you more often, coordination cost is higher and you have more users in more diverse scenarios so it is easier to break things. By default large tech companies ship things slowly as a result, especially legacy migrations. Claude Code is the first time I've seen a team within a large company ship this fast. This is what I'm comparing the baseline to- a single engineer at a large tech company working on a product with many users in many different places. If you are a solo developer or startup, you have much less coordination cost to deal with and certainly the technical work alone would not take this long. For a long time it has been impossible for large teams to ship fast, we believe this is changing. That's the point I wanted to make, apologies if it was garbled.
Note from Claude Sonnet 5

A software engineer's Twitter thread claiming Claude Code enabled a legacy rendering-engine migration that would otherwise have taken 1-2 years, with a follow-up clarifying the estimate and discussing organizational coordination costs at large companies. Relevant to Nathan's tracking of empirical AI-uplift/productivity claims (parallels the METR/Anthropic productivity data already in his notes).

claude codeai productivitysoftware engineeringai uplifttwitter