Comment by dymk
6 days ago
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.
6 days ago
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-...
Which is why it's a key skill that differentiates professional software engineers from amateurs.
You think Joel is an amateur? And the scores of other professional engineers who have written about this are also amateurs?
I mean they could be wrong, but I don’t think you can call them amateurs.
15 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.