This is a lie, unless you are just speaking of the mechanics of cursorily skimming it. Reading code to understand it enough to commit it in my name is harder and slower than writing it myself.
I don't commit entire libraries as written by me. Documentation is also far easier to read. Reviewing PRs is quite involving, since I want to do it well. Easier than typing code for sure.
The problem is not that I don't know how to do it. I am just asserting that Effort(Reading Code) > Effort(Writing Code) especially if `git blame` will spit out my name, not saying anything about their absolute difficulty.
This is a lie, unless you are just speaking of the mechanics of cursorily skimming it. Reading code to understand it enough to commit it in my name is harder and slower than writing it myself.
So you don’t use any libraries in your code?
How about reading documentation?
Or reviewing PRs?
Or go through source code to build out new features?
I don't commit entire libraries as written by me. Documentation is also far easier to read. Reviewing PRs is quite involving, since I want to do it well. Easier than typing code for sure.
Firstly, you are not the other poster, so I don't know how you can say it's a lie with conviction.
Second, reading code to understand it is a skill that you need to practice to get better at. That might be your issue.
It’s not the OP’s issue. That reading code is harder than writing it is as close to a consensus belief as we get in this industry.
https://www.joelonsoftware.com/2000/04/06/things-you-should-...
17 replies →
The problem is not that I don't know how to do it. I am just asserting that Effort(Reading Code) > Effort(Writing Code) especially if `git blame` will spit out my name, not saying anything about their absolute difficulty.
But creating a mental model and then interacting with it is slower than interacting with a mental model you already have.