#11. Make friends <i>at your current job</i>-- as many as possible, preferably with some being "diagonal-up" (e.g. not your boss, but at a higher level). Bonus points if they are unlikely to be cut. You will need them as references if your boss gives you a bad one (which you should check 3-5 weeks after being laid off, using a professional ref-checking service).<p>Friends from the old company are not just potential references, but also possible co-founders or recruits at the new job.<p>#12. Move all your side projects onto off-work computers, and try to make sure that they're deleted from your work machines nightly and automatically. (Of course, this is not the time to do something moronic, so only delete true side projects, e.g. things that the company doesn't know or care about but that you still need to unambiguously own for future purposes.)<p>#13. This one applies mainly to large companies. In good economic times, you want to make yourself as replaceable and obsolete as possible (write well-documented, easy-to-follow code) so you can move on to more interesting projects and, if laid off, leave on good terms to a better job. In bad economic times, try to make yourself irreplaceable, even if that means making your code difficult to use. If you feel the need to be unethical, you can hide time-delay bugs. At worst, you'll be asked to train someone else in the technology and offered a severance package in order to do it, which is better than being let go cold.