Nice paper that summarizes the historical papers related to concurrency models.
interesting looking conference on June 2-5 in london
fun interactive CPU component lesson
Well, OK, then.
Went in to the bank with Phoenix when she opened her account to see if they could just attach me to it as well somehow. Sure enough, the woman opening her account said that as long as I had a BSN, there was no reason I couldn’t open my own account, despite what we’d been told earlier. So now we both have Dutch bank accounts and are just waiting to get our chip and pin cards in the mail (along with hardware two-factor authentication devices!).
She also handles insurance and we figured out that (not surprisingly) the insurance that we’d had to take out before we could rent our apartment (Dutch law) was overpriced. Not surprising since we had very few options to pick through that we could get from the US before we had our completed residence permits, BSNs or domestic bank accounts. We’re stuck for a year, but then we can switch to a plan that’s about a quarter the price.
pull down environment variables from etcd and run a process with them
“only way to stop is to crash. only way to start is to recover”
Not interested so much in smartwatches, but the explanations of UX terminology are good.
Talk by Google’s SRE Czar.
Writeup from a Google SRE on alerting/monitoring. Very well thought out.
Pages should be urgent, important, actionable, and real.
This is good for thinking about Hound. Overall, a lot of effort has gone into making all of Hound’s alerts be “urgent, important, actionable, and real” but some fall short. Eg, quite a few currently exist that aren’t really actionable (eg, monitoring of various LITO services, Wardenclyffe -> PCP failures), that we have because we’d just rather know when something we depend on fails before our users.
Things to consider adding to Hound based on this:
Another good Joe Armstrong talk.
Will require a bit more of a social network concept functioning with followers/etc. But it would be good to be able to designate that posts in a channel can only be viewed by users that you have specifically designated.
Allowing a user to edit their posts wouldn’t be hard, technically. I’m kind of thinking that I like the current setup though, where you can delete, but not edit. It encourages you to not put too much into a single post. It also fits with the “publish” nature of the site. Once you’ve hit “submit”, it’s kind of like sending an email; anyone else could get/read it immediately. So you should think before you submit instead of after.
As of last week, Phoenix and I have our Dutch resident ID cards (good for two years), are officially registered with the city of Utrecht, and have our Burgerservicenummer’s (BSNs), which are the tax ids.
We still need domestic bank accounts (we were waiting on BSNs) so Phoenix can get paid, we can pay our rent in Euros, and we can get chip and pin debit cards, which a lot of kiosks and stores here basically require. Unfortunately, it looks like I may never be able to get one. The woman at the bank claimed that I could not open an account without an employment contract with a Dutch company. It seems like there’s probably a way around that, but in the meantime, we may only have one account between us.
imgur details how they are making mp4s out of gifs
explaining transducers using JS.
Free ebook on debugging Erlang systems.
Algorithms for approximate consensus. Nodes can asymptotically all converge on (roughly) the same value with very small amount of inter-node communication.
Hello there!
Finch is my new super-simple micro blogging platform.
I just want somewhere to very quickly dump random links, ideas, and code snippets without all the overhead of a proper blog setup. Stuff too big for twitter but too random to put on my main blog.
It’s written in Go using a sqlite database.