I can't decide if I'm happy or not that non-coding skills can leave such an impression. I'm still at my first job (I'm only a HS senior), and for the interview

I can't decide if I'm happy or not that non-coding skills can leave such an impression. I'm still at my first job (I'm only a HS senior), and for the interview I was asked to bring in some code. I brought my laptop, whose splash screen proudly displayed "Crunchbang Linux". I believe this was the moment that gave the most "points" in their eyes. Then I opened up my code, did some basic-but-impressive-looking flying around with Vim (it's not like there was actual editing involved), popped over to a terminal to `cd' around and then run it, and left a very good impression. And my PM has a habit of asking me for help with bash. I have a rudimentary-at-best knowledge of it, but he's happy when I kludge together something with pipes and grep and sometimes "after that command, vim will open. You should then press the following to find and replace the text as desired." I'll then include as a footnote, "There's a much better way to do this as a one-liner with sed and awk...I just don't know how." So of {beautiful code, working product, knowledge of tools} they only value two...and I'm just surprised it's the last two, not the first two. I guess I can't complain though.