co_pl_te

8 ms·

1. 61.▲
   The History of Python(python-history.blogspot.com)

   2 points by co_pl_te 13y ago|0 comments
2. 62.▲
   Two envelopes problem(en.wikipedia.org)

   11 points by co_pl_te 13y ago|1 comments
3. 63.▲
   Carl Sagan(en.wikipedia.org)

   2 points by co_pl_te 13y ago|0 comments
4. 64.▲
   A Tour of Rails’ jQuery UJS(robots.thoughtbot.com)

   1 points by co_pl_te 13y ago|0 comments
5. 65.▲
   Kleptography(en.wikipedia.org)

   3 points by co_pl_te 13y ago|0 comments
6. 66.▲
   Unfolding the box model, gorgeous slides on CSS 3D transforms(rupl.github.io)

   3 points by co_pl_te 13y ago|0 comments
7. 67.▲
   'It's too expensive'; three little words that are killing gaming(digitallydownloaded.net)

   2 points by co_pl_te 13y ago|0 comments
8. 68.▲
   Authors accuse Apple of destroying Japan's tech industry(globalpost.com)

   1 points by co_pl_te 13y ago|0 comments
9. 69.▲
   With Great Joy(randsinrepose.com)

   1 points by co_pl_te 13y ago|0 comments
10. 70.▲
    Collaborative effort to analyze the Adobe passwords dump(passwords.io)

    17 points by co_pl_te 13y ago|17 comments
11. 71.▲
    Picking up where you left off(brianbailey.me)

    1 points by co_pl_te 13y ago|0 comments
12. 72.▲
    Anatomy of a password disaster – Adobe’s giant-sized cryptographic blunder(nakedsecurity.sophos.com)

    6 points by co_pl_te 13y ago|0 comments
13. 73.▲
    Zeros in JavaScript(zero.milosz.ca)

    62 points by co_pl_te 13y ago|87 comments
14. 74.▲
    Catching Invalid JSON Parse Errors with Rack Middleware(robots.thoughtbot.com)

    1 points by co_pl_te 13y ago|0 comments
15. 75.▲
    The Latency of Dialogue(medium.com)

    1 points by co_pl_te 13y ago|0 comments
16. 76.▲
    Innovation Imperative: Change Everything(nytimes.com)

    1 points by co_pl_te 13y ago|0 comments
17. 77.▲
    What is Will Shortz thinking?(jimhblog.com)

    1 points by co_pl_te 13y ago|0 comments
18. 78.▲
    Responsive design, screens, and shearing layers(unstoppablerobotninja.com)

    2 points by co_pl_te 13y ago|0 comments
19. 79.▲
    "Form follows function" is more complicated than iOS7 thinks(blog.jaredsinclair.com)

    1 points by co_pl_te 13y ago|0 comments
20. 80.▲
    How an epic blunder by Adobe could strengthen hand of password crackers(arstechnica.com)

    2 points by co_pl_te 13y ago|0 comments
21. 81.▲
    Top Six Reasons to Use API Keys(stormpath.com)

    1 points by co_pl_te 13y ago|0 comments
22. 82.▲
    Twitter as a blank canvas(ben-evans.com)

    1 points by co_pl_te 13y ago|0 comments
23. 83.▲
    Your work is not good enough(hugogiraudel.com)

    3 points by co_pl_te 13y ago|1 comments
24. 84.▲
    Understanding the Threats in Cyberspace(schneier.com)

    5 points by co_pl_te 13y ago|0 comments
25. 85.▲
    by co_pl_te 13y ago

    Git is certainly capable of this, but I don't think that makes a service like Penflip that focuses specifically on collaborative writing superfluous. I like to code and I like to write, but I'd be much more likely to put a Rails a
26. 86.▲
    by co_pl_te 13y ago

    It depends. I like using Markdown for writing. Being a 'writer' does not preclude one from being a 'techie'.
27. 87.▲
    by co_pl_te 13y ago

    Love this. Actually working on something similar ('GitHub for storytellers') as my first Rails project. I have to learn a lot more to get mine even presentable, though.
28. 88.▲
    On the exploitation of APIs(blog.learningbyshipping.com)

    4 points by co_pl_te 13y ago|0 comments
29. 89.▲
    Oded Ezer, Mad Typographic Scientist(printmag.com)

    3 points by co_pl_te 13y ago|0 comments
30. 90.▲
    25 Years Since Women Needed a Male Co-Signer(thestoryexchange.org)

    2 points by co_pl_te 13y ago|0 comments