All that code you write for the man you'll never see again when you leave. Limit your pride, but not your quality of work of course. This includes limiting over

All that code you write for the man you'll never see again when you leave. Limit your pride, but not your quality of work of course. This includes limiting overwork. If your financial situation and the market allows for it, find a job that is not over taxing, and if you're a programmer by hobby and have the time, write some open source stuff. Aside from career benefits, it is fulfilling to review code you wrote in the past instead of just corporate memories of it. It's extra rewarding if you're like some people that, while you improve, your past code is still of very high quality. If you're the type that relishes leaving a legacy, just be mindful of its visibility.