Reviewing my old hacker news comments, saw this thread. So. A word to the wise. When you can't communicate what you've done, you are the person with the commu

Reviewing my old hacker news comments, saw this thread. So. A word to the wise. When you can't communicate what you've done, you are the person with the communications issue. It does not help to be defensive; it actually hurts. A source line of code counter can do a lot of things. You've neatly failed to communicate what you did in your resume, communicating "wc -l". You claim it to be a CLOC-esque program, which does not stand out to me. Fair enough, maybe my reading and inference skills need improvement. But, don't let me infer the wrong thing in your communications, especially in relation to a resume.