msherry

8 ms·

31.
by msherry 12y ago
"a little over half of which are in that bright sliver of Midtown, while the other half are strewn across the country supporting Times Square operations from designing the content on the signs to keeping the power plants that power the
32.
FCC to Verizon: ‘All the kids do it’ is no excuse for throttling unlimited data(washingtonpost.com)
4 points by msherry 12y ago|0 comments
33.
by msherry 12y ago
I presume it's a reference to https://en.wikipedia.org/wiki/Arrow_of_time .
34.
by msherry 12y ago
Time Machine to a local Synology Diskstation w/RAID, plus Backblaze. Will also chime in that I have nothing but love for Backblaze -- every time I've needed them (small files only, never a full restore yet), they've worked fl
35.
by msherry 12y ago
When I saw this, I first thought it was an extension of https://news.ycombinator.com/item?id=5326159 ;)
36.
by msherry 12y ago
More like SiftScience is a weaponized version of something a lot of companies develop in-house, I would say.
37.
by msherry 12y ago
I don't want to hijack this thread too much from the original post, but we use some of the same software as Airbnb (scikit-learn, randomforest models, etc.) as well as some stuff developed in-house. Credit card fraud has been one of ou
38.
by msherry 12y ago
(I don't work for Airbnb, but work in a similar space) Yes, this variable is usually set after the fact. For instance, a given transaction may have led to a chargeback, or may be done by a known fraudster. These models are usually trai
39.
by msherry 12y ago
I think you raise a good point here -- Gittip is run by committee and consensus, via Github issues and pull requests. The Linux kernel is developed via community as well, but has a strong leader at the helm to direct things. In contrast to
40.
by msherry 12y ago
That's always been my favorite response to him, as well. It made me tear up a bit reading it. Here's the thread, for anyone interested: http://www.metafilter.com/119424/An-Operating-System-for-Son...
41.
by msherry 12y ago
Did you read the article? "From a data-driven perspective, this is nothing short of maddening. There are many ways to board a plane, with “back-to-front”—the chosen boarding process of most U.S. carriers—the slowest."
42.
by msherry 13y ago
They're worthless because clearly no one is using them. They may theoretically be useful, but it doesn't matter if they're never put into practice.
43.
by msherry 13y ago
Sure, but I if as an inventor can't be guaranteed some protections for my work, for at least some period of time, I'm less likely to produce this better form factor in the first place, which is a net negative for consumers.
44.
by msherry 13y ago
Yup -- you can authorize a card with a missing, or even incorrect, CVV. I work at Balanced payments, and this frequently trips up a lot of people. If incorrect CVV information is entered, we note that in our response, but it's up to th
45.
by msherry 13y ago
I get that you were being flippant, but apparently Turkish is unusually hard to localize for: http://www.codinghorror.com/blog/2008/03/whats-wrong-with-tu...
46.
by msherry 13y ago
http://qntm.org/responsibility is an interesting go at it, and where I first learned of the concept. His other fiction is pretty fun, as well.
47.
by msherry 13y ago
Same thing happened to me. Presumably I can restore the older version from a recent backup, but this is pretty weak.
48.
by msherry 14y ago
Ahh, I see. Right, 950+ is the number of unit tests we have, each of which contains a number of assertions. If we count those, it's well into the thousands, so I guess the original question wasn't that far off the mark.
49.
by msherry 14y ago
Hi there. Why would you expect 5000+ tests, or anything more than 100? It seems like the number of tests that is the "right" number would be very dependent on the size of the codebase, which wasn't mentioned in the article. We write tests w
50.
by msherry 14y ago
If we're already at the "Oh shit" stage, then we might be happy sacrificing test coverage to go back to known-good code, in which case we would run our fabric `deploy` task and have our rollback completed in ~30 seconds. The idea behind thi
51.
by msherry 14y ago
The whole idea behind this testing infrastructure is so that we're fairly certain that any deploy isn't going to leave us scrambling to revert to an earlier version. Since we've implemented it, we haven't had to do that yet -- it's caught a
52.
by msherry 14y ago
Hi there. I'm the author of this post. We use git, so it's easy to revert commits, or push an update with '-f' that resets to an earlier version. Once we push this new commit (that simply puts us back to an earlier state) to our release bra
53.
by msherry 14y ago
This is basically what we did, except during the "upgrade the application and database" step, we suspended all traffic to our app servers. The schema change was an incompatible change (I think this is what you mean by "resolve data continui
54.
by msherry 14y ago
Thanks! We had been practicing on test servers and so we had the commands ready to be repeated, but you're right -- for reproducibility, a script would have been the way to go.
55.
by msherry 14y ago
You're definitely correct that bugs in the new application code would be a showstopper. Another bit of infrastructure we plan to write about if there's interest is our testing setup. Basically, before any deploy (not just drastic ones like
56.
by msherry 14y ago
You make a good point re: fault tolerance. As it happens, I've simplified the diagram quite a bit to make it simpler to visualise. We have more than 2 Nginx instances, and more than one shard of our app was running the new code.
57.
by msherry 14y ago
We actually have much the same functionality. We can dynamically route/rate-limit requests on a per-marketplace (or anything else, really) basis, using Nginx's Lua integration capabilities. We may end up writing another post on this, if the
58.
by msherry 14y ago
Sure, this definitely isn't the right approach for all migrations everywhere. When we have migrations that we know will take a long time, we try to make them non-invasive enough that we can have code that works with old and new schemas simu
59.
by msherry 14y ago
Are you saying it would work without code changes by increasing the timeout limit? We had to deploy new code to work with the new schemas, since the underlying models went through drastic changes. Having our code be compatible with old and
60.
by msherry 14y ago
Amazon being PCI-compliant was a requirement for us using them in the first place :) We could have possibly made a case for their PCI-compliance obviating the need for us to do our own SSL termination, but that could have gone either way, d

More ›