News for hackers. Stuff that matters.
Re:Reasonable Person Principle by rdtsc on Friday February 17, 2017 @04:34PM (#13671888)
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?

Re:Reasonable Person Principle by kiscica on Friday February 17, 2017 @05:00PM (#13672080)
That is odd. Maybe it's an in-joke alluding to database triggers or something? https://en.wikipedia.org/wiki/Database_trigger
Re:Reasonable Person Principle by rdtsc on Friday February 17, 2017 @05:12PM (#13672157)
Oh you may be right. I couldn't see the pattern right away though. Is it memory resident databases, and it is a pun on them not really being considered "databases"...?