lostphd

This is a great idea. Now that I think about it, it seems silly boasting how I've coded in so many languages. The reason I had them on my resume was to indicate that I have experience writing code in them. I like your idea of listing something under "Currently used" and listing the others under projects. That way, there is less chance for ambiguity.

Done :)

Thanks. I haven't seen that site before. I got cracking the coding interview (which seems too easy) and Elements of Programming Interviews (picked that up a few days ago and that book has some hand in shattering my confidence. Is that the bar for devs? If true, I freely admit I'm not at that level).

Some more data:

I study pretty much all my free time (time not spent with my wife). 2 hours a day reading papers, books, etc. I don't think studying more will help.

I can't post on github. Employment agreement says all the code I write belongs to my employer and can't be opensourced without jumping through some hoops. Won't make this mistake the next job I end up at.

I think I can move laterally without too much grief. I.e. get another research job. I have experience in systems and clouds. Lots of research groups would want someone like me.