2,120 karma · joined January 4, 2011
Github: http://github.com/yahelc
Personal: http://yahel.com/
Manger, Data Science & Engineering @ DigitalOcean.
We're hiring!
Email: yc -at- do.co
Worth noting that with Amazon SES, if you want to send more than 10,000 emails in a day, you'll need to apply (to Amazon) for approval.
And that's from Penn Station. Add the time it takes to get to Penn Station from where you're going, it can easily be between 1h30m and 2h. I did this trip yesterday, and from where I started in Soho until the airport, it was 1h45m.
Google Analytics' default attribution (outside of Multichannel Funnels) is last touch attribution.
I even posted an Ask HN asking if anyone remembered the name: https://news.ycombinator.com/item?id=8288303
--
Separately, FullContact API is also another replacement.
> If you’re actually reading this, here’s a treat. https://wordpress.com/tos/treat/
I failed to notice it (but had Find-and-replaced the domain), and got an agitated email from a user complaining that my "treat" link was broken. Needless to say, I was confused.
Further, there's little evidence that Debt-to-GDP over 100% (despite "feeling" meaningful, because, 100%!) has any kind of predictive value for the long term direction of an economy, particularly one that has unusually low interest rates. If Debt-to-GDP were a problem for the US, you'd expect higher interest rates, not lower ones, as investors would be demanding higher returns on US debt.
The fact that interest rates on Treasury bonds remain so low, despite our debt levels and despite certain political figures repeatedly attempting to force the US Government to default on that debt, is prima facie refutation of the idea that no one in the market actually thinks US debt levels pose a major macroeconomic problem in the short to medium term.
With id="submit", throws a "object is not a function" error. http://jsfiddle.net/nbkHs/
Without, submits just fine: http://jsfiddle.net/B8CV2/1/
> Your browser indicates if you've visited this link.
I was under the impression that browsers try to block sites from being able to detect this. Traditionally, the hack has been with the :visited pseudo-class, but not sure if there's more at play here.
Kind of a weird feature for a search engine whose tagline is "The search engine that doesn't track you."
Every test had a distinct set of JavaScript tags that had to be individually implemented for every single test. You had to place the scripts on each of the pages, and then verify that all 3+ of the script snippets are in the correct place (and if your test failed validation, you couldn't launch it). Making changes on the fly was difficult. If you misconfigured your goal, your data was forever lost (and you couldn't know if you misconfigured your goal until the data came through, and that wasn't in real time).
Contrasted with Optimizely, for every project, there's a single global JavaScript snippet that goes everywhere. No need to change snippets for every test. You can configure your tests from one place. And, for page-view level goals, you can add goals after an experiment starts, and they'll retroactively apply experiment data.
For a simple test, you can implement an Optimizely experiment in less than 5 minutes and feel assured that everything is working immediately, since it has real time data. If you need more power or complexity, it's there, but if you don't need it, it doesn't get in the way.
(Disclosure: I've been using Optimizely for nearly 4 years and recently spoke at their user conference.)
I don't think this is correct. Stripe (and the Stripe Admin UI) gives you enormous power to charge/upgrade/downgrade/enroll existing customers.
I'm curious, why did you choose to implement your own subscriptions, instead of utilizing Stripe's? This is a much more appealing option if its a clean integration that simply leverages all of Stripe's features (MoonClerk does this well).
very interested in using it.
http://sqlfiddle.com/ sort of does this, but not in the way Dataclips does.
Sharing the documentation links for the benefit of others, since it's not easily found:
Documentation for the query() function: https://support.google.com/drive/answer/3093343
Query Language Reference: https://developers.google.com/chart/interactive/docs/queryla...
https://www.google.com/search?q="for+the+modern+man"
Note how all of the results are all about men and manliness, which is fine for gendered products and clothing, but doesn't really make sense for a piece of server monitoring software.
Only reason I didn't file a PR myself was I wasn't sure what the best replacement would be (dev? sysadmin?), but this should be easy enough to fix if they're amenable.
EDIT: "Developer" as an alternative was merged very quickly. https://github.com/scoutapp/scout_realtime/pull/7