6 ms·
This is an example of engineering by lawyers. To get rid of this, I recommend the follows - a mandatory "minimum reading period" given for any document, that p
by zdw 13y ago
This is an example of engineering by lawyers.
To get rid of this, I recommend the follows - a mandatory "minimum reading period" given for any document, that prevents it from being turned in, calculated from the average HS graduate reading speed.
Also, before any meetings regarding revisions of said document, everyone involved in revising the document must A: be present, and B: serially, read a copy of the document, invoking the reading penalty multiple times over.
Optionally, to avoid this process, the document can be totally scrapped and replaced with an entirely new document, provided the new document is limited to 1/10th the reading length.
This would greatly reduce the amount of stupid long documents, and I see no downside.
- jamesaguilar 13y agoYou'd have to start by simplifying the legal code. Part of the reason that these long legal documents are necessary is the huge variety of theories of liability that companies are exposed to. If you want to avoid long disclaimers, you also have to remove the things companies need to disclaim to avoid huge legal expenses.
- seldo 13y agoThe first thing we do, let's kill all the lawyers. http://shakespeare.mit.edu/2henryvi/2henryvi.4.2.html http://shakespeare.mit.edu/2henryvi/2henryvi.4.2.html
- jamesaguilar 13y agoEveryone likes to blame the lawyers, but is the companies and non-company organizations that lobby for complicated laws to be made, and who employ lawyers to sue each other.
- lmm 13y agoIt's a classic tragedy of the commons. Every little special case in the law helps the organization that lobbied for it, and hurts everyone else.
- cdjk 13y agoUnfortunately the legal is perfectly clear... to lawyers. I've thought that it would be nice to simplify things, but it already is simple to the people for whom it matters (i.e. lawyers and judges). It would be kind of like trying to make a scheduler clear and obvious to someone who isn't a kernel developer, or at least very technical. You could get the basics across, but there'd be plenty of corner cases you'd miss.
- eitland 13y agoBut most of us don't have to sign off schedulers. Most of us are supposed to sign documents full og legalese once in a while.
- antiterra 13y ago> and I see no downside. Is this satire or have you not thought this through?
- NegativeK 13y agoTo quote what a lawyer acquaintance recently mentioned: if I'm an organization and someone signs my contract and then sues me, any vagueness in the contract will come back to fuck _me_ in the ass.
- fiatmoney 13y agoHe's right - the legal principle is contra proferentem. http://en.wikipedia.org/wiki/Contra_proferentem http://en.wikipedia.org/wiki/Contra_proferentem
- zdw 13y agoPartially satire. Partially frustration. Our society has decided as a whole to allow certain people to waste everyone else's time, with no penalties. We need some practical way to implement those penalties.
- pavel_lishin 13y ago> This would greatly reduce the amount of stupid long documents, and I see no downside. But it wouldn't reduce the number of documents that are long because they are documenting something very complex. The privacy statement may be 3,000 pages because the author(s) were (collectively) incompetent, or because medical privacy is a highly complex field that has a lot of gotchas, and therefore requires a lot of legal logic to cover it all.
- haldujai 13y agoAs a programming analogy, you could theoretically: 'refactor' contracts (simplify them) but it would create numerous 'bugs' (loopholes). To fix that you have to apply hard-coded bugfixes because the 'modules/classes' (laws) you are 'importing' (citing) are not open-source (so you can't fix them yourself) and you cannot create more to supplement exising ones in an elegant way. And that's how we get convoluted contracts.
- jlgaddis 13y ago> I recommend the follows ... Yeah, that won't work either and I'll tell you how I know. Anecdote 1: Almost everyone who uses a computer has encountered a EULA that one must click-through. We all ignore it and click "OK" or "I Agree" anyways, right? Recently, I've encountered a few that won't let you proceed until you really have "read" it. They "enforce" that by not letting you click-through until you've scrolled down to the bottom of the textbox. The first time I encountered this it took a split-second to figure out, I hit Ctrl-End, and <TAB>'d over to "OK". I thought about for a minute then hit "Back" a couple of times. I handed the laptop over to Stephanie, who was sitting next to me on the couch. "Hey, install this real quick for me while I run to the bathroom", I told her. When I came back a moment later she says, "That was weird." "What?" "I had to click the scroll thing on the license all the way to the bottom before it would let me install." "That is weird," I said. "What'd the license say?" She gave me a "are-you-serious?-like-i-actually-read-that" look and my experiment was complete. She's certainly more technical than most people but I'd wager that my mother (who certainly isn't) would also quickly figure out to simply scroll to the bottom to bypass it without actually having to read it. Anecdote 2: Several years ago, my then-fiancée, was required to take a four-hour online "driver education" course because she had received greater than "x" citations in "y" time. For each section, you had to read a wall of text and then answer several questions afterwards. You were required to spend "x" amount of time reading it -- you couldn't proceed to the questions until that time had passed. Lindsey just sat on the couch watching episodes of one of her shows on the DVR and every few minutes she'd look over at her laptop, click to the next page, and answer the questions. She didn't bother reading any of the text and once she got to the next section, she'd sit the laptop back down and go back to watching her show. At the next convenient break in her show, she'd click "Proceed" and answer the questions. Rinse and repeat. Anecdote 3: I worked at a .edu for several years and also taught many courses during my time there. On a few occasions, in the middle of a random block of text in a paper that I would hand out for the students to read and answer a few questions over, I would insert something like "draw a peace sign next to your name for 10 bonus points". What I was interested in is whether they were actually reading the paper or simply jumping straight to the questions, reading the question and then quickly skimming the paper to try to find the answers. I didn't keep statistics but I'd say that perhaps 10-15% of the students would get the bonus points on a good day. --- Now all of these are anecdotal, sure, but I think it illustrates quite well that us humans are quite capable of finding ways around whatever roadblocks stand in the way of whatever we want. In recent years, it seems that humans in general have become more obsessed with instant gratification (I am certainly guilty of this) and/or we've just become lazy. When I was in school, I did not want to spend an hour reading a paper when I could instead jump straight to the questions, skim over the paper in search of the answers, and be done in 10 minutes either. In short, I don't think there is any foolproof way of completely ensuring that someone reads a document. Don't underestimate fools. =)