Perlin actually improved his original algorithm by creating the Simplex Noise http://en.wikipedia.org/wiki/Simplex_noise which runs much faster. As a matter of interest, Voronoi noise is also quite popular
I hope this works out for you. I've taken up learning vim this year, but my main problem is forgetting the things I've learned. I tried cue cards but they fill up far too quickly; so my answer was to store my notes on a wiki: http://wiki.jbud.me/index.php?title=Vim
Vim is too big to learn. Eventually you'll muscle-memory a set of actions, for the way that you uniquely use vim, that you don't even know how to explain without thinking about it.
Rather than trying to go through one end of a tutorial or reference to the other (don't know if that's you), find a site or two of vim tips, and let them randomly trigger your mind. I think it's more interesting than going through anything beyond page/chapter 1 of a reference.
Coupled with that, whatever you find yourself doing in vim, take some time to understand what it is and the alternatives. Becoming familiar with :help's table of contents, rather than the contents of every chapter, is probably helpful here.
Similarly, when you do something accidentally, try to understand what happened. Sometimes you'll discover a feature. q: for example is discovered by accident by many people, including me.
I find that some of these limitations put me in a worse position than if I were to have full control. eg. you MUST use a symbol, or using both lower AND upper case characters.
This is a joke! We're in the 21st century, people should be able to have their own set of password standards. I know we, as programmers, are always looking out for the most noobish of the end-users. But is it really necessary to go as far as to FORCE EVERYONE into picking a blatantly obviously brute-force-safe password?
In the end, the bulk of these users are just going to forget their password, add it to their password manager, and become frustrated with this chosen system. This in turn is insecure for its own reasons.. I think what we need is to remove these silly limitations altogether (although a set standard minimum/maximum character limit is completely understandable imo), and allow people to pick their own standards. The newbies out there will eventually get their accounts hacked, its inevitable imo. And when that happens they will learn to set better passwords.
The last official test I did, a couple years ago, stated just over 100wpm..however just last year I had a data entry job which required some SERIOUS typing speed. New employees would get introuble if they couldn't keep up with the others (who, most of which, had been there since before I was even BORN!). I can feel I've definitely gone up since that summer
The main 3? You're actually missing ASP .NET which is quite popular (in fact, isn't it 2nd place in popularity to server side languages?) .. Please add this, otherwise you'll be getting A LOT of 'Other' votes
This tutorial was totally cool! Props to the guy who made this, and for doing something like this while in his bored spare time... 1 complaint however is that it doesn't explain much about the difference between MongoDB and MySQL, or other databases. I was really hoping to get to hear how it compares, what the pros and cons are out of using this vs. other databases