links for 2011-04-25

  • There has been quite a bit of research in both academic and practitioner circles into the impact of personality types on agile teams. Various commentators have asked variations on the question “is there an agile personality type”. The most common answer seems to be “it depends”, but there seem to be some key characteristics that seem to indicate an affinity with agile methods. 
  • Last Thursday Facebook announced the Open Compute Project where they released pictures and specifications for their Prineville Oregon datacenter and the servers and infrastructure that will populate that facility. In my last blog, Open Compute Mechanical System Design I walked through the mechanical system in some detail. In this posting, we’ll have a closer look at the Facebook Freedom Server design.
  • I've been toying with the idea of looking for an alternative to Intellij for Scala development for a while now. I tried to use Ensime with Emacs a few months ago and never got it going for one reason or another. More recently, I've got Ensime and Emacs working together and thought I'd blog about it for anyone else who had trouble getting everything to work together.
  • So, whatever I am going to do, it should at least (1) allow me to wrap a DB object in a Map and (2) allow me to transform keys and values to the appropriate type. I want to be able to access a Kyoto Cabinet DB as a Map[Int,Date], – if I feel like it.
    Instead of addressing both concerns inside a single class, I eventually opted for factoring it out into separate classes. It seemed having a mutable Map abstraction that on the fly transforms its keys and/or values to an alternative type would be useful in other circumstances as well.
    (tags: scala)
  • Browsable Scala source code in HTML with:
    – syntax highlighting
    – types/applied implicits in tooltips
    – references/definition highlighted on mouseover
    – links to definition
  • Paper's core proof re: transactional operation is useful. Somewhat spoilt by a poor conclusion that essentially says "can be solved with hardware" which has been proven false many times. An environment of independent failures can be created with enough cash but probability is such that two independent failures can occur simultaneously and wreck your plans.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: