4 ms·
Why isn't "write documentation" in that list? I mean sweet Jesus, it's 2023. Write some fucking documentation. There are also these things called comments that
by manv1 4y ago
Why isn't "write documentation" in that list?
I mean sweet Jesus, it's 2023. Write some fucking documentation. There are also these things called comments that you can put in your code so you can explain why you're doing what you're doing.
The code shows what, the comments show why. And it's the why that's important.
Anyway, the more code you read, the better you get at figuring out what code does. But instead of reading the code try to understand the intention behind the code. Think of it as you're reading the mind of the person writing it. Are they lazy? Bad? Overly complicated? Weird structure? What do they always do? What are they bad at? How do they approach what they're doing?
There are developers who are too clever by half, and you can see it in the code; they do something in a complicated way instead of doing it the simple way. They do things that look interesting but which have no real benefit.