3 ms·
Nah, I stand on the shoulders of generations of developers, just like everyone else here. I didn’t claim my opinion was novel, just that it’s mine. I hope othe
by aaronbrethorst 4y ago
Nah, I stand on the shoulders of generations of developers, just like everyone else here.
I didn’t claim my opinion was novel, just that it’s mine. I hope others share my opinion, because I’d find codebases that fit my criteria easier to maintain than many other types.
Also, do you agree or disagree with any of the ideas I put forth?
- Karellen 4y agoI don't disagree, I just think it's only right to credit the original authors when you use their exact phrasing.
- Rexxar 4y agoI think we have a problem if we need now to credit the original "author" of every opinion we have.
- aaronbrethorst 4y agoWhich original authors am I unintentionally plagiarizing? I’m not usually that adept at quoting verbatim, especially when I’ve completely forgotten who I’m quoting.
- Karellen 4y ago> programs must be written for people to read and only incidentally for machines to execute. -- Abelson & Sussman, The Structure and Interpretation of Computer Programs, 1984 FWIW, I already provided the quote, with the source, in these comments, 3 hours before you wrote yours. (ok, it's not exactly verbatim. But I think it would get counted as plagarism in almost any context reasonably imaginable.)
- aaronbrethorst 4y agoAhh, I apologize for not thoroughly reading the entire comment thread before posting mine. Otherwise I would've upvoted you and said "+1" or something to that effect. I certainly didn't mean to hurt your feelings. And also thanks for jogging my memory on the source. SICP remains one of my favorite textbooks from college, although it's been about 20 years and so everything's fuzzier than it used to be. Have a great weekend.