I appreciate all of the feedback and will be incorporating a lot of it.
what did you mean by a wc replacement?
>You're not an expert - if you are, you'd not be looking for entry level positions, and you likely wouldn't be a hobbyist. You'd probably have a history of consulting in your expert field.
Seriously, everyone is failing on comprehension on that one sentence. I'm an expert in my field looking to pivot to another. Expert SYSTEMS engineer. I'm changing the sentence to prevent future misreads.
> Seriously, everyone is failing on comprehension on that one sentence. I'm an expert in my field looking to pivot to another. Expert SYSTEMS engineer. I'm changing the sentence to prevent future misreads.
If one person calls you a skunk, ignore them. When two people call you a skunk, sniff. When three people call you a skunk? You're probably a skunk. ;-) (edit: you totally miscommunicated. that's why everyone is reading it the way they are).
Also, `wc -l` gives you line count: I've written it half a dozen times in half a dozen ways on half a dozen different systems. it's really easy.
not a pure line count. a program that counts lines of actual code. excludes comments, tracks lines of code that span multiple lines in the text editor, ignores whitespace lines.
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.
what did you mean by a wc replacement?
>You're not an expert - if you are, you'd not be looking for entry level positions, and you likely wouldn't be a hobbyist. You'd probably have a history of consulting in your expert field.
Seriously, everyone is failing on comprehension on that one sentence. I'm an expert in my field looking to pivot to another. Expert SYSTEMS engineer. I'm changing the sentence to prevent future misreads.