is this my future?
is this my future?
buses in vancouver look like grasshoppers. when viewed from above at least. the two metal pantographs which join them to the overhead power cables looks like antennas. just so you know.
oooh - comic fest in vancouver in a few weeks. i might just go along to this.
[best](http://www.bash.org/?41232) bash of the day: <poserman> what is considered a long distance girlfriend? <poserman> 10, 15, 20 hops???
vancouver airport is by far the most beautiful i have seen. by really really far. clean crisp lines, beautiful structure and bizarre indoor outdoor scenes, with a mini-waterfall scene. unlike anything i've ever seen. people should learn from this. the only other airport that's interested me was paris cdg - a huge concrete spider, with a web of moving walkways in the centre. fun, but feels old. vancouver feels new.
aren't they building some hyper-architectural airport in china somewhere (spotted in wallpaper), or was that a seaport?
only a few days in vancouver and i find myself hoplessly addicted to jolt cola. with a seven-eleven about 10 metres from the office, i'm doomed to a sugary death. yay!
you know what's really dumb? livejournal's atom implementation. rather than use easy auth (http basic) or the atom spec'd auth that's annoying but possible (wsse) they use fucking http digest auth - the least documented thing on the web. does anyone know any decent explanation of how to implement http digest auth on the client side? the rfc is a maze of tiny rooms, all alike.
yet another a beautiful shirt from threadless. i'm a bit cautious about buying this one though, since these crazy foreigners get easily offended. i'm having to resist shouting "fucking cunt" at my pc every few minutes. good job i didn't bring my "intellectually rape me" shirt with me :)
finally got atom wsse auth working. turns out i was doing everything right, except i was using an sha1 hex string output instead of the raw binary output. it would have been nice to actually specify this in the fucking spec, since most sha1 libraries output the hex string version. urgh.
i'm not sure if there's anything that makes me madder than xml-rpc (maybe atom's wsse auth, but i'll get to that). the idea is sound, but it's very badly designed. very badly. to return a single hash of data, you end up with a tree six elements deep. why have <value><string>bob</string></value> when you could just do <value type="string">bob</value> ? It's almost as if the designer didn't want to use a full xml parser, so avoided anything that couldn't be parsed with a regexp. yuck.
This is the personal website of Cal Henderson, Slack co-founder & CTO.
I give occasional talks, write code and sometimes articles.
ai aws books color covid emoji fonts games halflife hardware havana ibm japan lego maps math minecraft music php reading tube via-matts via-momorgan wiring
apple awesome bacon code coding comics design flickr food games javascript lego maps movie music perl php programming software tech tv video visualization web