3 ms·
It’s not that I’ll assume the internals are not going to change. I just don’t trust the docs to be accurate anymore. The implementation contains an accurate de
by danielheath 2y ago
It’s not that I’ll assume the internals are not going to change.
I just don’t trust the docs to be accurate anymore. The implementation contains an accurate description of what it actually does.
I still read the docs… with a grain of salt.
- jajko 2y agoMan, sometimes I would give some gold for some documentation, even 10 years old. Half-irrelevant, doesn't matter. At least something. Sometimes, I don't have even that. That's what drowning in complexity looks like since there are some many question marks and often nobody anymore to answer them. Even stellar code just tells me whats going on. Doesn't tell anything about why its happening, what consequences does it have in other systems, what are the overall constraints of this domain etc. I agree generally too long comments aren't best, or even just non-flexible rules. But denser the logic is, the more spread its across multiple systems and environments, the more info the better. And to be changing some dense code and completely ignoring comments just next to it describing them... that's just rude to be polite. Shows who is a team player and who isn't. Trust me, if you want to make friends and have some respect in some long term team, this is one sure way how to do it.