- Strategic Dialogue Management via Deep Reinforcement Learning (Adrian Colyer) — a neural network learns to play Settlers of Catan. Is nothing sacred?
- scala school — Twitter’s instructional material for coming up to speed on scala.
- Robin Hood Fellowship — fellowship to use technology to increase access to legal services for New Yorkers. Stuff that matters.
- The Echo From Amazon Brims With Groundbreaking Promise (NY Times) — A bit more than a year after its release, the Echo has morphed from a gimmicky experiment into a device that brims with profound possibility. The longer I use it, the more regularly it inspires the same sense of promise I felt when I used the first iPhone — a sense this machine is opening up a vast new realm in personal computing, and gently expanding the role that computers will play in our future.
Everyone wants an alternative to email, but do we really need one?
Editor’s note: this post originally appeared on Medium; it is republished here with permission.
Conventional workplace wisdom declares email a daily scourge. We receive too much of it. We spend too much time replying to it. We concoct elaborate strategies to cope with it and avoid incurring a debt that downward-spirals to email bankruptcy.
We bow down at the altar of Inbox Zero, the methodology that dictates we take prompt, concrete action to dispatch with every single message we receive. Reply to it. Or file it. Or delete it. We turn the drudgery of processing the flood of correspondence into a game. Inbox Zero, FTW! Achievement unlocked … till the next time we hit refresh. Because emails are like gray hairs: for every one we send packing, five more will soon arrive in its place. Any client-side strategy we take to conquer our inboxes is thus limited by the fact that it’s palliative, not ameliorative. Perpetuating Inbox Zero means living in a constant state of vigilance, aggressively and swiftly responding to every incoming message. It means becoming an email answering machine!
One speaker at Fluent 2013 whose talk was particularly well received was Todd Kloots of Twitter who spoke about HTML5’s pushState API and demonstrated how it was used in Twitter’s Web-based interface.
Some key parts of Todd’s talk include:
- The opportunity Twitter saw in pushState [at 01:45]
- What you had to do with dynamic URLs before pushState [at 02:46]
- A summary of the pushState API [at 06:10]
- Gotchas and browser support [at 07:58]
- How pushState sped up navigation on Twitter.com without re-architecting [at 12:15]
- What Twitter had to do server-side to make progressive enhancement work [at 19:11]
- Final thoughts [at 31:37]
- Q&A [at 32:15]