Heh, I feel like "someone" ought to write the Big List of Bad First Projects for This Language, e.g.:<p>Go/Erlang/Elixir: "Testing" the concurrency by parallelizing the addition of an array of integers via some sort of sending single integers over messages, or in the worst cases, literally spawning entire processes/goroutines/etc. to add two ints (and then wondering why the concurrent program fully consumes all eight CPUs but is still twenty+ times slower).<p>Go (as of this writing): Immediately trying to implement a generic data structure.<p>Rust: Complicated pointer-type data structures like linked lists, or goodness-forbid, doubly-linked lists.<p>Haskell: Starting right off by trying to implement an in-place sorting algorithm.<p>Python: Taking your C numeric algorithm and converting it into pure Python (and then being shocked at the performance).<p>Criteria for my inclusion is that I personally have seen each of these many times.<p>It's not that these tasks are necessarily impossible, or even necessarily all that hard when you know what you are doing, just that they are <i>bad first tasks</i>, but they seem to tempt people for some reason. For example, someone reading a Python tutorial hasn't heard of numpy, if you're just learning Rust immediately learning how to break the rules you don't fully understand yet isn't the best use of your time, etc.<p>In this particular case it all turned out OK in the end, but it often doesn't go this well. :)