License files.

People don't read them.

They are longer than they should be.
Mostly to hide evil shit the developers are doing.

I am now going to start including the complete works of Shakespeare in my license files.

This means it will have evil shit other people have done included in the file. Will most likely make it meaningless. Nobody will read it anyway.

At the very end I will just write: Don't be a dick.

But you do understand that it’s not our part of job to read, nor to understand them and is purely for corporate lawyers?

@bagfox I partially disagree. We are the ones that choose what libraries to use, and to make sure (or at least sort of calculate) that what we are doing is (for the most part) legal. Imagine that the company lawyers had to check every release if we added any library or if any of the licenses changed (cause some projects change license with the next version). I mean, that would be the correct way of doing stuff but it's not practical. Pre-written libraries make it easy for devs and I hate custom libraries

@eo2875 I have worked at places where I was instructed to "ignore licenses". I always tried to follow licenses even then. We gotta keep our bosses outa trouble, and us!

@Demolishun "You don't care about licenses? Awesome! I'll use GPL 3 for ours."