skiplist1

The problem with people that believe that being reasonable is the reasonable thing to do is that many crucial moments of our lives depends on taking irrational moves. I remember someone saying that the way to win in a game in which both of you are chained together at the edge of a mountain and the first one to take rational moves lose is to dance while singing at the edge of the mountain. Like in poker we need some irrational moves to win in society. Also, America was discovered because someone make a trip to nowhere.

Since I was a child I thought that programming could be the amazing tool to create something that should be a breakthrough and would make me rich. I am still struggling to find that magical key, so I am not bored at all!

Just an honest question. Can I obtain some estimation of the capabilities of CS people working for the government by just reading all these code. Will I find here a glimpse of code beautifully designed and tailored to solve some really deep problem that require real intelligence?, can I use these code to learn how to code a big project?

I would like to see a language like haskell with no delayed or lazy evaluation so that one can better predict performance. Haskell has a great community and a charm that I would like for Ocaml. Don't know if Jane Street is still advocating their Ocaml core or kernel. F#, ml, haskell and OCaml, and a strong language for parallelism whose name I don't remember are hints that we need a better language. Haskell is not prepared for real world :), and OCaml is a turtle moving target.

I just skimmed over skiplist in point 10 of your book. The concept and definition of skiplist is easy to grok and it is well explained but in point 10 there is not any information as to when should I use a skiplist, what kind of problem a skiplist is a good tool to use. I have bookmarked your page, it seems to be a useful resource if it is complemented with a comparison and use case for all these data structures.