3 ms·
Let me know when you meet a person that can handle 1.5M lines, because most people I've worked with can't. Certainly I've never worked on something that require
by vineyardmike 1y ago
Let me know when you meet a person that can handle 1.5M lines, because most people I've worked with can't. Certainly I've never worked on something that required even reading that much... Especially when targeted search options exist to find just specific function/class implementations as needed.
- stickfigure 1y agoI have a large team that works in a 1.5M line codebase. Not everyone is familiar with every line, but we regularly make changes that would blow through the usable context window of LLMs (which is, in fact, much smaller than advertised). Is a messy 1.5M lines of tightly coupled code best practice? Of course not. But it evolved over about 20 years and processes tens of billions of dollars of financial transactions. In my experience, it is archetypical of real-world software for a large successful company. I use LLMs where I can and they're incredibly useful. But their limits are severe compared to a good human software developer and the shortcomings mostly revolve around their tiny context. Human neuroplasticity is still champion.
- yyhhsj0521 1y agoSure, they work in that huge codebase, but for any specific task, the number of lines your team keeps in their short/long term memory is surely much much smaller than that.
- ignoramous 1y ago> 1.5m line codebase I work regularly with AOSP code (~3mn). While LLMs (Copilot w/ Claude Sonnet 3.7, in my case) cannot gobble all of it up, they have no trouble answering my queries, for the most part, from submodules. If nothing else, using LLMs has dramatically reduced the time it takes to understand a new code file / submodule / a range of commits.
- stickfigure 1y agoI'm going to wildly guess that AOSP is part of every LLMs training set, so that feels like cheating somehow :-)