3 ms·
Pure coincidence. Like those random unimportant memories that get stuck with us, but we don't know why. When you work in really large projects, which are not h
by rantanplan 13y ago
Pure coincidence. Like those random unimportant memories that get stuck with us, but we don't know why.
When you work in really large projects, which are not hobby projects, with specs you don't even understand
the reason of their existence, it is impossible.
For example I have many experiences similar to what you described, yet today I couldn't remember why I did
something in a code fragment I wrote last week.
That's why you'll see all great programmers sharing similar stories. Otherwise you'd be superhuman.
Pure coincidence my friend.
- MartinCron 13y agoI guess it could be pure coincidence. But I'm going to chalk it up to the fact that I go out of my way to have well-factored code that uses intention-revealing names and isn't too clever for its own good. The choices that you make when writing code really do matter.
- rantanplan 13y agoAll things you mentioned are considered given, for someone that is an above average programmer. Yet in large projects, with lots of people, with many interconnected modules, clear code and concise variable naming is not enough. That's why we have documentation that describes the general architecture and comments for the code parts that aren't so clear cut. Some problems have many solutions, with different levels of advantages and disadvantages. To think that all people understand or know the solutions and the choices pertaining to them, is of course naive. To think that you, as a person, would choose the same path at different instances of time, is just entertaining. You are not the same person you were last year, or even last month. Thus, good comments along with clear and concise code is the only way to go.