Key-person dependency risk is when only one person on your team possesses certain business-critical abilities or knowledge—so if that person leaves, you're in trouble. The first step of mitigating that risk is taking stock of your team members and their skills. Decide what's important, and train or hire accordingly.

In a job interview, you learn a fair amount about the job you’re applying for. But it’s much harder to learn about the corporate culture so as to determine if the organization is a place you want to work. Try using a "good cop, bad cop" routine when asking questions to find out if the new environment is a good fit.

If you want to be a thought leader in the software community, you may want to share your expertise by getting published. But no matter how knowledgeable you are in your particular domain, writing about it is another matter entirely. If you're struck by writer's block, try writing a letter to unblock your thoughts.