← Back to context

Comment by simonw

7 days ago

Only if you're not very good at reading code. If you've invested a lot of effort in improving your code reading and code review skills you can work a lot more productively with LLMs than people who don't have good code reading skills.

So you think that reading code is harder, but if you put in equal amounts of practice at reading and writing code you’ll get faster at reading code than writing code?

Sounds to me like you don’t think reading code is harder.

  • I think reading code is harder than writing code.

    I think that if you put the work in you can get to a point where you are fast enough at reading and reviewing code that it's not a net productivity loss to have an LLM - or your coworkers and collaborators - write code for you to review, as opposed to insisting on writing every line of code yourself.

    I'm a little surprised that my opinion about this is seen as controversial!

    • Your position is confusing to me as well.

      > if you put the work in you can get to a point where you are fast enough at reading and reviewing code

      Please correct me if I'm wrong, but "fast enough" here would still be slower than writing the code yourself (given equal amounts of practice at reading and writing code), right? To throw some made-up numbers around: if it would take me 20 minutes to write code to do X, it might take me 30 minutes to read/review code that does X written by somebody else (or an LLM), so I'm at a net loss of 10 minutes. Can you explain the mechanism by which this eventually tips into a productivity gain?

      Personally, I think "reading code is harder than writing code" lacks nuance. While I believe it's true on average, the actual difficulties vary wildly depending on the specific changeset and the path it took to get there. For example, writing code can involve exploring many solutions before eventually discovering a concise/simple one, but when reading the final changeset you don't see all those dead-end paths. And reviewing nontrivial code often involves asynchronous back and forth with the author, which is not a factor when writing code. But please take the "reading code is harder than writing code" claim for granted when responding to the above paragraph.

      9 replies →