new blog post - functional specifications for infrastructure engineers  http://d2fn.com/2013/01/28/functional-specifications-for-infrastructure-engineers.html …

if this gets 1000 RTs i will literally eat a panther

"look at this lovely javascript codebase!" -- no one ever

the reason we get excited about software and libraries and such is that we assume they work which is false

jvm atomic versus volatile on x86  http://brooker.co.za/blog/2012/11/13/increment.html …

you have been convicted of writing an asynchronous program. your punishment is to be determined.

lmao if you don't think your consciousness is immediately accessible by a very large fish elsewhere in the universe

here are the slides for my #ricon2012 talk on distributed systems radiology. sorry, MRI animations not included. https://t.co/dKz2h8p4

as of this week, any data you see on the @boundary dashboard older than ~10s is served directly out of kobayashi / #riak

if you're planning to build a distributed system with riak_core, there are worse places to start than here --> http://t.co/rrGBxim

i just came to see if anyone on twitter is mad hi

the kobayashi query engine is now based on an olap language i've been working on per the @boundary tech talk http://t.co/MiVJ8wUF #riak

i made a thing to dump and restore zookeeper data today https://t.co/Q9Try5wf

someone once said "i have a problem. i know, i'll solve the problem with networked computers". now they have an unknown number of problems.

computers.
dogs.
computerdogs.
http://t.co/qHpZ259f

it's not that #minimalism is so great, it's that most of us suck at building something complex that isn't tasteless garbage.

¯\_(ツ)_/¯ https://t.co/WDZIMLGr

#concurrency #wisdom #disruptor http://t.co/FUu4KTXH

just wrote a new blogpost on debugging a distributed database by looking at the network (to be cont.) http://t.co/OKZnUzW4 #riak #leveldb

"@boundary shows how few of us can even tell where all our software begins and ends anymore." http://t.co/6mVwKb4K