The problem is that lying on a resume is very closely related to a situation that will arise in most development jobs and which can really damage a team. Consi

The problem is that lying on a resume is very closely related to a situation that will arise in most development jobs and which can really damage a team. Consider a developer who is in a status meeting and is behind or having trouble with their current project. Someone who lies on their resume is much more likely to be one of those people who try to cover it up, lie about the current status, or shift blame. It means that the project lead is always going to be second guessing their status reports and unsure whether to really trust their estimates. I hear this stuff all the time, "yeah, it is almost done, I just didn't get it checked in...". Probably code for having major problems or sometimes not even having started it. If you get in a work environment with many of these characters, life sucks.