Shinichi Mochizuki's homepage is worth a look :) http://www.kurims.kyoto-u.ac.jp/~motizuki/top-english.html

The general message there is "I'm always up in the skies working on my proofs. No office hours this week"

"I’m no doctor, but I’m afraid you be exhibiting symptoms of illin’." :)

Talk to one of the pictures. :)

Well, I didn't know there was a standard... for me it just felt "I know more Javascript than Haskell etc" so I put one more black square. So maybe I should change it to 2 out of 7 or whatever. :/

Aliz, I guess I was responding to the OP comment about resume's more than anything and didn't mean to offend. I really like your use of a scale, and your project is very impressive!

Don't let pedantic nerds get you down. It's fine. Full disclosure: I too am a pedantic nerd.

Wasn't trying to be pedantic, just giving feedback. In fact I totally respect the relativity of the scale, I would just say if it was for a job interview you'd want to maybe do as you said and adjust on a larger scale.

My point was 2 months in JS != 40% knowledge of JS. If that came across as pedantic, I apologize.

It might be a weighted 40%. As in, she knows 40% of what she needs to know or will encounter in real-world JS... or she's 40% as productive as she'd be with maximal fluency. There's probably a Zipf's Law over programming idioms where you can pick up the first half in a few months, the next quarter takes a year or so, and the last quarter takes more than a decade to encounter, comprehend, and be able to use masterfully.

Using a frequency-weighted metric, I would say that I'm 70-95% fluent (unknown unknowns make it hard to get confidence in a number) in my best languages, but I'm not an expert in any of them (and I'd only rate myself 3-3.5 on a 5-point scale, because percentage fluency on first-order concepts isn't the only important thing). I don't think it's hard to get to that point. Getting those last few percentage points is much harder.

Yup, I started studying bioinformatics in 2010. I chose bioinformatics, because I was interested in biochemistry and biology and wanted to learn how to code. To my disappointment uni did not teach me much practical things and programming courses (Haskell) were really boring. I would find myself sitting over a really dull homework in the middle of the night thinking "It's so stupid and boring. I really don't want to do this. I want to do more fun stuff... like coding a game or so.". Well trying to code a game in Haskell turned out to not be the best idea. Especially if you don't know how to code yet... and then I just stopped going to classes. 3-4 months ago I wanted to make a band, but had a hard time finding musicians. So I decided to learn Rails and HTML etc to build a web application which could help me (and others) find some musicians. In the end I never really officially launched it but learned a lot and found that I enjoy coding. :)

I'm learning Haskell using http://learnyouahaskell.com/ and I don't find it boring at all. Nowhere near as boring as homework.

Don't blame it on Haskell. Everyone has to learn the fundamentals. Haskell is suited for making games, it's just not the mainstream language for that. See http://www.haskell.org/haskellwiki/Frag . Yes, 3D games have lots of tricky state handling and OpenGL doesn't map well to Haskell. But doing a point-and-click adventure in Haskell is not harder than doing it in C++.

I really doubt your classes were stupid and boring. Maybe you were the one who was stupid and boring :P

I have to say I like Haskell and I don't think it's boring at all. I just wanted to learn more than they were teaching us in uni. :) Haha, I even played around with HOpenGL...