This talk by Chris Granger is superb. I’m definitely going to spend more time learning about CRDTs. My favorite tidbit from the talk (around the 8:55 mark) – Apple’s auto layout in iOS uses a linear inequality constraint solver.
Apache ZooKeeper has become an indispensable component for many distributed systems: Apache Hadoop, Apache Mesos, Apache Kafka, Apache HBase, etc. all use ZooKeeper in some form or the other. I’ve written code that interacts with ZooKeeper and I’m a big fan of the simple APIs and powerful guarantees it provides.
I had a vague idea of the broadcast protocol that powers ZooKeeper but wasn’t awake of the details. So this weekend I decided to read a short paper that gives an overview of Zab (a more detailed description of Zab can be found in “Zab: High-performance broadcast for primary-backup systems” by Flavio P. Junqueira, Benjamin C. Reed, and Marco Serafini).
The title of the paper is extremely accurate – Zab is a very simple protocol that is intuitive and easy to understand. The paper does a great job of explaining the core concepts of the algorithm to the reader. I particularly liked section 3, which includes a comparison between Zab and Paxos. Section 4 is probably the most important section of the paper and is very well written. The figures illustrating the two main failure scenarios are a nice touch.
Next step – read the detailed Zab paper.
One of my goals of 2014 was to learn a new programming language, and for various reasons I decided on Go. While my learning progress has been pretty terrible for most of the year, I was able to make pretty good progress this week.
What made me get to 40% this month? Several things, but by far the most important one was A Tour of Go.
I feel that the Tour could be improved by adding three things – syntax highlighting to the code in the console, more exercises, and including solutions to the exercises. Apart from that, I think it is a perfect learning resource.
My thoughts on Go? I think it is an interesting language, and something that I will most certainly delving into more. I’d read some Go code before (mostly Docker code) so I was vaguely aware of what the language looked like. I was initially a bit hesitant about the fact that Go has both high level (e.g. functional programming) and low level (e.g. pointers) features, but I think I quite like this ability to have and use both. The concurrency primitives look excellent, and I can’t wait to write some code using it. Another thing that scared me a little was the lack of classes, but structs + interfaces seem to be powerful enough to deal with that. I’ve read online about Go’s lack of generics being a problem, but I haven’t written enough code in Go to comment on this issue. I really liked the fact that the Go compiler doesn’t allow you to compile code that has unused imports or unused variables.
I read about TDD and it’s associated red-green-refactor cycle while learning Ruby on Rails and I was quite intrigued by the concept. It seemed like a novel way to approach programming. From what I read on the Internet about it, it also seemed to r…
I read about TDD and it’s associated red-green-refactor cycle while learning Ruby on Rails and I was quite intrigued by the concept. It seemed like a novel way to approach programming. From what I read on the Internet about it, it also seemed to reduce bugs in the code and generally leads to better, more human understandable code.
So, when we were given our first programming assignment in CS 241, I decided to approach it with the TDD mantra. Programming this way was a great expirience, once I had come up with enough test cases for my assignment, programming it up wasn’t too hard because I had already captured all the edge/unusual cases.
All in all, I was satisfied with this approach, and I will most definately be using it again for future assignments when possible.
So we had ‘picture day’ in Phil 102 today. I was talking to the instructor about an article I found and wrote my name down as “CS” on the board instead of my slick moniker “KP”. Thankfully, I caught this error in time. Sometimes I wish life had sy…
So we had ‘picture day’ in Phil 102 today. I was talking to the instructor about an article I found and wrote my name down as “CS” on the board instead of my slick moniker “KP”. Thankfully, I caught this error in time.
Sometimes I wish life had syntax highlighting built in.