Try rakudobrew and play with concurrency

rakudobrew is similar to perlbrew, but it’s for Rakudo (a.k.a., Perl 6), the Perl-inspired language that we’ve all come to have a love/hate relationship with. I urge you to try it out, but first, some interesting new developments that you should probably know about…”

http://blogs.perl.org/users/ovid/2014/08/try-rakudobrew-and-play-with-concurrency.html
https://github.com/tadzik/rakudobrew
https://github.com/tadzik/panda

Learn Lisp The Hard Way

“Complete beginners to programming, who want to be assured of learning a powerful language that will help them develop unique insights of their field. Someone who has struggled with programming before. Hobbyists, who are looking for a new challenge. A professional developer looking to take their performance and productivity to the next level. In a word, everyone…”

http://learnlispthehardway.org/

Randomized Binary Search Trees

“I have always been surprised by the contrast between the grace of the main concept of binary search trees and implementation complexity of balanced Binary Search Trees (Red-Black Trees, AVL Trees and Treaps). I have recently looked through the “Algorithms” by Robert Sedgewick [1] and found a description of randomized search trees (I’ve also found the original [2]). It is just one third of a page long (nodes insertion, and one more page for deletion). There’s also a nice implementation of the operation on deleting nodes from a search tree. Here we’ll talk about randomized search trees, their implementation in C++ and also results of a small author’s research as for these trees balance…”

http://kukuruku.co/hub/cpp/randomized-binary-search-trees

On Machine Learning

“Recently, I wrote how we do classification at CB Insights. The post outlines some of the things that I have been thinking about how to apply machine learning for a given problem along with the process that we adopted for the classification problem at CB Insights, but also gave me a good opportunity to reflect even further about the machine learning process; shortcomings of papers, books and even traditional education system when it comes to teach the machine learning.

My aim is not to focus on the algorithms, methods or classifiers but rather to offer a broader picture on how to approach a machine learning problem, and in the meantime give couple of bad advices. I will offer my bad advice for a classification problem(algorithm=classifier) and be warned that they may generalize better than your favorite classifier.(I will try not to overfit, but let me know if I do so in the comments.)…”

http://bugra.github.io/work/notes/2014-08-23/on-machine-learning/

Understanding Paxos

“The first time I heard of the Paxos algorithm was during my bachelor’s degree way back in 2004, when I participated in a Distributed Algorithms course. In the past few years Paxos came up multiple times, usually in the context of a robust implementation of some scalable storage system. It is almost always uttered in awe, as to say “that unbelievably complex algorithm, the Paxos. Beware!”. I’ve decided to reread the original paper, and try to explain what Paxos does, and how it does it. In a nutshell, Paxos solves the problem of resiliently replicating an increasingly growing (ordered) list of items…”

http://distributedthoughts.wordpress.com/2013/09/22/understanding-paxos-part-1/

“The previous post gave a general overview of the Paxos algorithm. Here’s a quick recap: Paxos implements a resilient distributed log, such that items can be added and each item is assigned a unique (and increasing) index. The algorithm can be split into three main blocks: a leader election, a consensus on a single item (also called the Synod algorithm) and managing the entire log. In this post I want to go into more depth about the Synod algorithm…”

http://distributedthoughts.wordpress.com/2013/09/30/understanding-paxos-part-2/

 

Using TCP keepalive with Go

“If you have ever written some TCP socket code, you may have wondered: “What will happen to my connection if the network cable is unplugged or the remote machine crashes?”.

The short answer is: nothing. The remote end of the connection won’t be able to send a FIN packet, and the local OS will not detect that the connection is lost. So it’s up to you as the developer to address this scenario…”

http://felixge.de/2014/08/26/tcp-keepalive-with-golang.html

Writing a Simple Garbage Collector in C

“People seem to think that writing a garbage collector is really hard, a deep magic understood by a few great sages and Hans Boehm (et al). Well it’s not. In fact, it’s rather straight forward. I claim that the hardest part in writing a GC is writing the memory allocator, which is as hard to write as it is to look up the malloc example in K&R.

A few important things to note before we begin. First, our code will be dependent on the Linux kernel. Not GNU/Linux, but the Linux kernel. Secondly, our code will be 32-bit and not one bit more. Thirdly. Please don’t use this code. I did not intend for it to be wholly correct and there may be subtle bugs I did not catch. Regardless, the ideas themselves are still correct. Now, let’s get started…”

http://web.engr.illinois.edu/~maplant2/gc.html