Here's an interesting perspective: Code Is Not Literature http://www.gigamonkeys.com/code-reading/
It addresses a puzzle:
> [So many programmers say], “People should read code” but few people seem to actually do it. I’d be surprised if I interviewed a novelist and asked them what the last novel they had read was, and they said, “Oh, I haven’t really read a novel since I was in grad school.” Writers actually read other writers but it doesn’t seem that programmers really do, even though we say we should.
@codesections i just woke up but for everything OP says is why literate programming is bad is alost why i say it's good, lol.
@emsenn @codesections I find that literate programming is a wonderful way of actually accomplishing the task. It's sort of taking the rubber-ducky problem solving method and applying it to the act of building in the first place.
People put a lot of hate on LP because they hate writing documentation/comments. I think we should have this whole topic nipped in the bud (so-to-speak) in school when it's being taught.
@emsenn @codesections Well, rubber ducking, as explained to me, is when you come across a problem you can't figure out, you talk to an inanimate object about the problem until you've figured out how to resolve it.
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.