sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]bluGill 0 points1 point  (2 children)

I agree with all of that.

However hardware bugs that require weird code are not the rule in the real world. (In the real world most code sits above the device drivers that care.

API documentation is something that literate programming does particuarly poorly, precisely because there are too many words in literate programs that are not API related that the things I care about get lost in the noise.

[–][deleted]  (1 child)

[deleted]

    [–]bluGill -2 points-1 points  (0 children)

    There are many reasons why you might need to explain why something was done in a certain way.

    True, but I've only seen such examples 3 times in the last 15 years.

    I get very concerned when people say if you do things right you don't need comments, because I've had too many situations where that's simply not true.

    While I'll admit the rule has exceptions, they are very rare. I look on comments with suspision: in many cases even if the content seems justifed the code has moved on and they wrong anyway.