Links Archives

  1. Heartbleed and Pinboard →

    In layman’s terms, the bug was the equivalent of asking a stranger “hey, what’s up?” and having them tell you their most private thoughts, going on about their divorce, sharing their credit card info, whatever was on their mind at the time. You could keep asking “what’s up” as often as you wanted, and hear new things each time. Worst of all, the stranger would have no recollection that it had happened.

  2. Hack Isn’t PHP →

    You’re effectively writing in a new language, albeit with a much smaller learning curve than other language switches since you already know most of the syntax and API. But because Hack isn’t PHP, some of PHP’s biggest advantages – ubiquity, maturity, stability – don’t apply.

    I agree with a lot of this. As well as the follow up.

  3. Obama May Be Best Economic President Ever →

    Here’s an interesting calculation: Suppose that in 1929, you put $100,000 in a 401(k) fully invested in stocks. Under the 40 years of Republican presidents, you would have ended up with only $126,000. Under the Democrats, you would have amassed a retirement nest egg of $3.9 million! (All numbers are adjusted for inflation.)

    There are some interesting numbers in here, worth fact-checking. I’ve always been in the “things are better when everyone is doing well” camp, regardless of where I’ve fallen on the scale.

    Also, from the :bang: department…

    Deitrick says he’s perpetually shocked that Democrats don’t trumpet their economic triumphs.

  4. The Difficulty of Selling Software →

    The question for Oracle and other companies that derive the majority of their income from software, rather than with software, is whether there are signs underneath the surface revenue growth that might reveal challenges to the sustainability of those businesses moving forward.


    Consumer software, enterprise software: it doesn’t much matter. It’s all worth less than it was. If you’re not adapting your models to that new reality, you should be.

    Most of the software I see being commercialized today is done so via services and other means. I still like the “direct selling of software” model, but I don’t see any point in swimming upstream on it.

  5. The Programmer Productivity Paradox →

    That is why developers that plan their code before using the keyboard tend to outperform other developers.

    I’m a big plan of pre-coding planning. There are 2 things I do when doing development:

    1. thinking
    2. coding

    Things go best when I’m not doing both of them at the same time. I use Capsule to help me with the thinking part, then switch over to my editor to get coding.

  6. OneNote To Rule Them All →

    Nice rundown by Justin. I’m still not using a “digital junk drawer” app – they all seem too laden with navigation to make getting to what I want efficient. I’m content with my NVAlt + Dropbox sync + Mobile apps and an “all text all the time” solution for now.

  7. Why I Recommend Writing For At Least An Hour A Day →

    But some form of regular writing is one of the best ways to give yourself time for reflection and analysis.

    This is the main reason I’ve been blogging for the last dozen years. I’ve also found that the benefits extend to coding – writing out what I need to clarifies it for me and helps me identify edge cases and additional things I need to consider. It gives me space to really think about the problem. I use Capsule to journal my coding.

  8. He knew he was wrong →

    If a cadet did something better than normal, his next attempt at the task would in all likelihood not be as good, whether or not he was praised. In the same way, if he performed unusually badly, his next attempt would probably be better, whether or not he was criticised. The trainer was attaching a causal interpretation to the fluctuations of a random process; simple regression to the mean.

    (thanks Micah)