Before modern AI coding assistants, how long would a typical junior or mid-level developer need to produce around 1,000 lines of code? I realize the work could involve SQL queries, CSS, HTML, and repetitive changes across multiple files, so I'm wondering what a realistic general estimate would be. I'm asking because AI can now generate thousands of lines very quickly, although that code still needs to be reviewed and tested.
4 Answers
More code is not automatically better. Code is something you have to maintain, test, and debug, so unnecessary lines can become a liability. A small, well-designed change—or even a pull request that deletes code—can be more valuable than thousands of lines of generated code.
The amount of code someone can produce also depends heavily on experience. Developers with a large library of patterns, utilities, and existing code can work much faster than someone starting from scratch. Even before AI, autocomplete, templates, and reusable components made repetitive work much quicker.
There isn’t a reliable number. It depends on the language, the task, how much design is involved, and whether the code has to be tested and debugged. A developer might write 1,000 simple lines in a few hours, while a difficult feature could take days or weeks and produce far fewer lines.
Lines of code are a poor productivity measurement. Someone might spend days solving a complex bug and change only three lines, or generate thousands of repetitive lines quickly with autocomplete and existing tools. Meetings, documentation, testing, and code review also take time but don’t show up in the line count.
That makes sense. I recently saw a change I made with an AI assistant add about 1,000 lines in a couple of hours, but the raw number doesn’t say much about how useful or maintainable the result is.