805 karma · joined July 1, 2015
(not affiliated in any way). https://trino.io/
This position is for the team I'm on, developing and implementing new ways to protect customers from bots.
I'm happy to answer questions about the position, the team, or Imperva, which acquired Distil Networks in the summer of 2019.
Apply here: http://app.jobvite.com/m?3xY9tlwX
Text below:
Customers may experience issues connecting to Slack to loading channels at this time. Our team is on the case and we will keep you posted. Apologies for any disruption.
Sure, AWS may be constantly innovating on doing things more cheaply and scalably. Sometimes, those savings get passed off to the customer; but not most of it, and not necessarily all that frequently.
Edit: added the link. https://nimbusdata.com/products/exadrive/pricing/
Hopefully there would be other good things about that universe, too.
Amazon tends to want every part of itself to be in ship-shape, and giving itself a massive discount would discourage efficiency in non-AWS parts of the business.
Disclosure: neither a current nor former Amazon employee.
It's also written in rust instead of Java, so there's no JVM RAM penalty or GC to contend with.
You could run it on a digital ocean droplet so you don't have to worry about your laptop turning off. It covers retry and cron-style job kickoffs.
This passage, and really her whole summary of the history of Google, (which goes beyond just this excerpt) are particularly compelling.
* Do you do batch and/or streaming computation?
* What kind of access do you have for querying/accessing the data this role will predominately be working using?
* Do you have dedicated data engineers and data infrastructure people
* What's your workflow orchestration engine?
* What is the data access pattern for historical data (there had better be at least SQL access here).
* Do you have built-in feedback loops for your machine learning products?
* What is your serialization format of record for production and for OLAP?
* How often do schemas change in your databases?
Additionally, front-line workers can see real problems with how customers experience the product that may not be reflected in the metrics used to evaluate the product, since metrics are inevitably gamed.
The ratio of good to bad ideas doesn't matter if you miss the one good idea you really needed. A company that invests in ways to effectively use the ideas of 'untrained people', as you so delicately put it, can derive a lot of value from those ideas.
I wonder what the retention incentive period was for Github employees; it's often a year, and the Github acquisition was mid-2019...
I use Presto all the time, I love how fully-featured it is, but garbage collection is a non-trivial component of time-to-execute for my queries.
We've probably crossed that bridge already, but this would certainly speed up that outcome.
If I subscribe to your API and get the outputs of your predictions, since I can see the kinds of inputs that you tell me are associated with preferring PayPal, I can approximate your PayPal-preference model.
This works for basically any machine learning model-as-service. So if I invest heavily in approximating and then serving models more at lower cost than anyone else, that might be a viable businese.