Makes sense. Good summary. I've heard it mentioned as "don't be a jerk", "don't first assume when others act like jerks they always meant to". The last part, avoids quick escalations of misunderstandings.
Interestingly just last year I remember someone posted the syllabus to the Advanced Database Systems: http://15721.courses.cs.cmu.edu/spring2017/ (latest version). Really good stuff there.
But one thing I noticed there was plenty of red triangles. Apparently those are trigger warnings. So I opened some of those papers, for example: http://15721.courses.cs.cmu.edu/spring2017/papers/04-occ/tu-... , expecting to see some horrible things, but I couldn't see what would be triggering there. There are transaction ids, commit phases, reads, writes, B+trees ...
So given that it is coming from same school, shouldn't the same "reasonable-ness" apply. Is it reasonable to sprinkle trigger warnings onto distributed database readings? I understand history, psychology, anthropology, literature, art might have disturbing contexts, but computer science?
Interestingly just last year I remember someone posted the syllabus to the Advanced Database Systems: http://15721.courses.cs.cmu.edu/spring2017/ (latest version). Really good stuff there.
But one thing I noticed there was plenty of red triangles. Apparently those are trigger warnings. So I opened some of those papers, for example: http://15721.courses.cs.cmu.edu/spring2017/papers/04-occ/tu-... , expecting to see some horrible things, but I couldn't see what would be triggering there. There are transaction ids, commit phases, reads, writes, B+trees ...
So given that it is coming from same school, shouldn't the same "reasonable-ness" apply. Is it reasonable to sprinkle trigger warnings onto distributed database readings? I understand history, psychology, anthropology, literature, art might have disturbing contexts, but computer science?