dweekly

47 ms·

1. 511.▲
   Four Typical Post-Product Mistakes(medium.com)

   2 points by dweekly 12y ago|0 comments
2. 512.▲
   Salary Fairy: Crowdsourced Salary Estimations(salaryfairy.com)

   1 points by dweekly 12y ago|0 comments
3. 513.▲
   by dweekly 13y ago

   Not sure where you see $12/year for 100GB? My pricing page shows $1.99/mo for 100GB => $23.88/year. Are others seeing different pricing?
4. 514.▲
   by dweekly 13y ago

   Not sure where you're getting that math. $5/year (current price) vs $1.99/mo for 100GB = $23.88/year, which is about 5x more than I pay now.
5. 515.▲
   by dweekly 13y ago

   Apologies for not being more specific in what I'm comparing. You're right that their TB plan is 50x my 20GB plan, but I was referring to their 100GB plan. Current plan: 20GB for $5/year ($0.41/mo) => $0.25/GB&#x2
6. 516.▲
   by dweekly 13y ago

   My point is - they used to have excellent $/GB plans (grandfathered), then reduced the value, and now have improved the value back to roughly what it was before.
7. 517.▲
   by dweekly 13y ago

   I currently pay Google $5/year for 20GB. I use half of this. I'm supposed to be really excited about what a good deal it is that I can pay five times as much for five times as much storage that I'm not using...?
8. 518.▲
   FB Growth & Analytics Speaker Series(facebook.com)

   1 points by dweekly 13y ago|0 comments
9. 519.▲
   by dweekly 13y ago

   http://www.wired.com/wiredenterprise/2013/12/apples-mac-mini...
10. 520.▲
    Taking QUIC For A Test Drive(connectify.me)

    3 points by dweekly 13y ago|0 comments
11. 521.▲
    by dweekly 13y ago

    Whoops; I'm an idiot. The request had a UA of LibreOffice. Looks like Dropbox has indeed moved on from Crocodoc. My bad.
12. 522.▲
    by dweekly 13y ago

    What a Dick move.
13. 523.▲
    by dweekly 13y ago

    Dropbox uses (used?) Crocodoc to do its document previews, which would be interesting now that Crocodoc has been acquired by Box (a Dropbox competitor). Crocodoc actually ran full Windows VMs to have Word interpret Word, unlike what was spe
14. 524.▲
    by dweekly 13y ago

    [nod] We'll look into it. Please follow / comment on the bug thread at https://developers.facebook.com/bugs/702273849788774
15. 525.▲
    by dweekly 13y ago

    (I also work at Facebook) We have systems that block spammy apps that are 99.9% of the time really incredibly sophisticated and get a ~0% false positive rate. This is a case of the 0.1%. :( Folks here are scrambling to undo this. Very, very
16. 526.▲
    by dweekly 13y ago

    Thanks, barce. I'm curious - by "using time communiting to learn" does that imply that a podcast would be the right form factor?
17. 527.▲
    by dweekly 13y ago

    OP here, some 5+ years after having authored that content and taught the class. Astonishing that this got surfaced - I was very surprised to receive a flurry of inbound requests to join a class I ran half a decade ago. I'd love to know
18. 528.▲
    by dweekly 13y ago

    I put together this very silly and trivial webapp last night in about fifteen minutes and put it up on GitHub for giggles too. https://github.com/dweekly/fontifier - pull requests accepted for other mutations / fo
19. 529.▲
    by dweekly 13y ago

    I posted this on my FB wall, pretty outraged, and a friend of mine who is a former federal prosecutor had this to say in response: Let me provide some context: this was certainly not unchecked or without oversight. In fact, any time phone r
20. 530.▲
    by dweekly 14y ago

    I'd hate to make a guarantee I couldn't stand by. Let me say this: they're all supposed to work - if you find some that are b0rk3d, please let me know and we'll fix/remove them.
21. 531.▲
    by dweekly 14y ago

    [nod] I think it's absolutely true that in the most stable relationships, both sides stand to gain. There is definitely much to learn from the pioneering work Amazon has done in this space. For what it's worth, I'd be very interested to hea
22. 532.▲
    by dweekly 14y ago

    (FB tool here) How can we make our documentation & communication not awful?
23. 533.▲
    by dweekly 14y ago

    Totally agreed that Parse kicks ass, which is why we bought them; we're looking forward to working with the team to continue to improve it! As a brand new member of the team, I'm really keen to hear more about how we've failed at our APIs
24. 534.▲
    by dweekly 14y ago

    [nod] But we did not buy Parse to kill it!
25. 535.▲
    by dweekly 14y ago

    I'm really sorry you've had bad experiences with the API. :/ I'm not sure how much consolation it will be to you, but we've gotten a lot better about this, even in the last year, increasing platform stability, improving our documentation, a
26. 536.▲
    by dweekly 14y ago

    Bummer. Can I ask why this changed your mind? At FB, we're quite serious about finding ways to gift third party developers with APIs, tools, open source, platforms, whatever we can do to help. I think Parse is pretty awesome and is likely t
27. 537.▲
    by dweekly 14y ago

    False. http://www.downforeveryoneorjustme.com/adobe.com
28. 538.▲
    Science and Religion(blog.dweek.ly)

    1 points by dweekly 14y ago|0 comments
29. 539.▲
    How To Handle Recruiter Calls(blog.dweek.ly)

    17 points by dweekly 14y ago|17 comments
30. 540.▲
    by dweekly 14y ago

    I'd love to field concrete suggestions for how to improve the likelihood of A) getting in front of people who have received bad takedowns and B) convincing them to get in touch / share information about their case. Friendlier copy? Actual d