I make it a point at any interview to go over this stuff when we get to the "Do you have any questions about us" portion of the interview. So far everyone has been very cool about taking care of such things in advance. Better to do it then instead of when things start getting bumpy and they start looking for stuff to hang on to.
One of the things that I started doing a long time ago was keeping an online diary of my ideas. When I come into a company, I list that diary as part of my previous work, so that I have a record that it's something outside of their company. I also make it a point to save emails with other developers that I've worked with, just in case. One thing nice about doing open-sourced developement is that there is an open record of what you've been doing.
So far I haven't had any ideas that a company has considered worth trying to claim as their own, but when I do, by golly, I'll be ready.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||