I get it, REST is a complex topic. Too many people think they understand it, and are falsely validated when they bump into other people who don't understand it. Folks everywhere are building RESTish APIs which are basically just RPC + HTTP verbs + Pretty URLs, and as that doesn't seem very helpful they write giant articles explaining why that's not very useful…

"The world works the way it works, not the way we want it to work. It's one thing to point at the flaws that make it hard to do cryptography in Javascript and propose ways to solve them; it's quite a different thing to simply wish them away, which is exactly what you do when you deploy cryptography to end-users using their browser's Javascript runtime."

“It seems counterintuitive that the masters take a humbler approach than amateurs. But we see it all the time.”

Best quote of the article

Going beyond simple A/B testing with interleaving

A really good talk about the software failure of the Therac-25 and how it translates in today's programming world.

A good introduction

Ruby love for classes and all we are all trying to get to the same place (separation of concerns).

“the ability to hold two opposing ideas in your head at the same time and still retain the ability to function.”

Coffee consumption seems generally safe within usual levels of intake, with summary estimates indicating largest risk reduction for various health outcomes at three to four cups a day, and more likely to benefit health than harm.

Let’s go over the thought process for solving a tricky coding interview question.

A very interesting description of what women need from men moving forward

very good points about critical software

It’s less like I’m surfing through channels and more like the TV is automatically flipping from channel to channel, reading my eye movement and facial expressions to decide what to show next.

TL;DR
How a team of less than 20 people managed to steal $81M from a central bank, without physical presence

Questions to ask during an interview

FizzBuzz in Ruby with nothing (except Proc)

Google Inbox suffers “proprietary creep”: non-standard, closed algorithms that promise to organize your life, an essential component of a lock-in based business model.

This document explores possible directions for data classes in the Java Language.

Interesting, in the future we might think less about finances, but also the social aspect of having algorithms too good to let risky users get credit.