"Why? Do you get extra points for doing things the hard way? As opposed to: choosing the right tool for the job."
I don't know what potential employers are looking for (and now I realize that I haven't even tried to find out), but I would expect them to be more impressed with a thing if I were to do it in a more 'difficult' language than if I did the same thing in a language that needed only two lines of code for the job. My focus is on signaling my skill, rather than completing the program itself.
Then again, I'm thinking it would be even more impressive to learn Python's deepest secrets and exploit them to the max.
Data point, possibly completely irrelevant: When I am looking for a Java programmer job in Slovakia, pretty much the only thing employers care about is how many years did I program in Java and which frameworks did I use. -- Which in my opinion is completely stupid, because I consider the ability to write and understand algorithms much more important; and a new framework is just something you can learn in a month or two, if your algorithmic skills are solid. I guess the problem is with the fact that the employers who make the decision are not coders themsel...
This is the public group instrumental rationality diary for September 16-30.
Thanks to cata for starting the Group Rationality Diary posts, and to commenters for participating!
Immediate past diary: September 1-15
Rationality Diaries archive