Here's the problem: the law of quickly diminishing returns.<p>Recently I've tried to "learn more" about one specific IP issue: what are the rules for Intellectual Property developed while being employed by someone but outside of work and not using employer's equipment?<p>I've read very informative discussion on <a href="http://answers.onstartups.com/questions/19422" rel="nofollow">http://answers.onstartups.com/questions/19422</a>, including authoritative-sounding response from Joel Spolsky and frankly, I don't think that in terms of knowledge I can act on with confidence about what the final outcome will be, I'm any smarter than I was before I've read it.<p>The bottom line seems to be: technically the company that employs me owns any IP I do during employment but if you're lucky you're not going to be sued.<p>And that seems to apply more generically: in most cases you can use your common sense (don't use other people's trademarks, don't write code for your future company at your current workplace etc.) but when things get contentious, it's anyone's guess what the final outcome will be.<p>I've got code to write and the time spent reading books on IP law (which is part of the advice that this article gives) is time not spent writing software.<p>What I need is not a book or 50 blog posts but a "1 day guide" to the most important issues which provides bottom-line advice and not only "this is what theoretically might happen" but "this is how it usually works out" (e.g. in the context of "who owns the IP developed during employment" the theoretical advice is "employer, so don't even think about bootstrapping your startup in your free time" but practical advice is "technically employer, but it's virtually unheard of employers suing ex-employees and many do it, so keep things quiet and bootstrap anyway").