I work on a product called Kazoo. Kazoo is written in erlang. Lately at work, those of us on the Platform team have been having a conversation about a language feature known as ETS (erlang term storage). The end of the conversation pretty much always concludes that
Erlang ETS == Magical
I have been down the road of finding a magical language feature (not in erlang) for a specific use case, only later to find out that when I switch the conditions of the use case, it totally and completely falls apart. With that in mind, this weekend I did a little reading / researching / googling to find the source of the magic.
Thanks for Erlang Solutions for posting the Videos from the latest Erlang Factory in Sweden, had a talk specifically about benchmarking ETS. This was really awesome, and anyone who cares about ETS should watch it.
tl;dw – ETS is MAGIC, however, if you are trying to scale a product using ETS, be VERY aware of the number of physical chips on the server vs. the number of cores on those chips. There are runtime flags to pin process schedulers to individual cores, but there are tradeoffs.
Thanks for the awesome doodle logo Google! Anyone who does not know the scope to which Grace Hopper affected all of our lives, should read her wikipedia page. Ending with the rank of Navy Rear Admiral, she coined the phrase “debugging” by getting a moth to be removed from one of the early computers (they liked the circuits apparently!). She invented the compiler, and argued (to much resistance at time) that programs should use english language to be more expressive. Any CompSci friends out there pining for writing in binary or hexadecimal still? It was cool also to read in that article that she tried to influence the DOD to move away from large centralized systems and use smaller distributed systems. Grace Hopper, we salute you and all your contributions to humanity!
The company I work for 2600hz presented at the highly touted TechCrunch Disrupt conference.
Here is a little video to find out more about what are are up to!
This website is hosting some very interesting conversations regarding distributed systems and topics on concurrency. The above link is to a conversation about Causality. The root of the conversation deals with how systems can maintain the consistency of a state of a database or a document. Warning: The conversation is very scholarly, but it does a really nice job at describing the current best theories on concurrent data systems.
I use BigCouch at the company I work for, 2600hz.com where we build Kazoo, a distributed communications platform for Voice / Video / Text etc.
I will no doubt be continuing to watch these conversations over at thinkdistributed.io
Another day down.
Rachel made me another spinach salad with goat cheese and chicken. Probably a cheat with the champagne pear vinaigrette dressing, but I still have to identify as human throughout this process right?
Dinner was a steak and steamed zucchini, broccoli, and mushrooms.
Missed breakfast today, and need to build that habit to really jump start my metabolism ( and more importantly do the same thing as my boy Liam).
Finished day 4 of the 30 day shred, physically I felt ok going into tonight, need to remember to push myself and not go through motions. Level 1 is still kicking my ass, so I think I should stay there until I can give a little ass kicking back myself.
On a spiritual note, I am finding that this process is making me feel better about myself and what else I am doing. I believe that my Heavenly Father Mother doesn’t make better material things, but he / she provides the essence of “care” and I should consciously recognize that I am reflecting that quality into the world. In the end Love takes us all the way, and I am actively tapping more into it