> The author can either explain it or doesn't understand it. I've never been challenged to explain any of the code my CV points to. I could have made it all up

> The author can either explain it or doesn't understand it. I've never been challenged to explain any of the code my CV points to. I could have made it all up. If they randomly asked about something I have not looked at in a long a while, it could actually look like I don't know it! There is so much of it that I would have to study the code as a full time activity to be able to fluently spout off about any random sample of it. I think I'm going to rearrange my resume to move the free software stuff farther down and maybe shorten it. It could come across as a negative. Some hiring people genuinely don't understand why someone would put in a 40 hour week and then do some more on evenings and weekends. Well, I don't know how many. In my career I heard something along those lines from around two. Not everyone will tell you. > You left college or high-school and walked straight into a job then learned to code there, or what? It doesn't describe me, but does almost everyone I've ever known in the field (other than distant strangers met through online free-software-related channels, who are an obviously biased sample).