HN user

nleach

85 karma
Posts17
Comments22
View on HN

[Context: I worked with this team previously] Data here is coming from mobile apps, and is similar in volume to typical mobile app user analytics. I can certainly imagine that Segment would be a poor (or maybe just costly) fit for device telemetry in most IoT use-cases.

It’s non-obvious, but that’s actually very close to how farming works today, at least in the US. Farm-owners will lease their land for a season to grow a specific crop. The land needs to meet requirements for acreage, irrigation, etc., but someone else will “use” the farm.

I’m sure this happens on a continuum from “that’s a big field, can I use it?” to “here are seeds, I expect XYZ yield in N months”.

IFTTT | Full-time | Software Engineer | San Francisco, CA (ONSITE) | https://ifttt.com/jobs

Are you a maker/hacker/tinker-er? Do you love Ruby _and_ type systems? Want to help scale one of the largest consumer-oriented serverless platforms? Join IFTTT!

IFTTT is the free way to get all your apps and devices talking to each other. Not everything on the internet plays nice, so we're on a mission to build a more connected world.

IFTTT is hiring for a number of engineering roles* but I’m selfishly plugging the systems engineering (more-or-less backend) role. We’re a high-leverage team building resilient systems that operate at scale. Help us thoughtfully break apart our monolithic Rails application into composable services that support our consumer-facing teams to deliver award-winning experiences.

If you’re in the Bay Area and want to learn more, shoot me an email at nicky@ifttt.com. Happy to grab coffee and chat about what we’re working on and how you can help.

* Are you a data, mobile, or infrastructure engineer? We’d love to talk to you too! I’m happy to connect you with the right folks here at IFTTT.

Mesos running on AWS, almost entirely with EC2 spot instances.

We were big Heroku users as well, so carried over a number of Heroku patterns. For example, configuring everything with ENV vars, lightweight load balancing, grouping apps into several deployable targets, etc.

It’s certainly not better than Heroku in most ways, though there was no plausible way for us to continue running our workload on Heroku.

(Edited: typo)

To add to silvamerica's comment, this process is specific to running containers in development. When building images for deployment the dependencies are installed as a RUN step in the Dockerfile.

Annoying, maybe, but I don't think it really fits with the theme of the rest of the list. Providing the user with a potentially helpful shortcut to an app doesn't really compare to breaking deep links for the mobile web.

In e-commerce, doesn't latency == $$? Is the bandwidth premium really that much higher? Or is the performance difference between the geographies negligible?

Interesting that the IP address resolves to their datacenter in Ireland. I would have assumed either Singapore or Tokyo. Is there any reason that a continental connection is preferable to an.. aquatic one?

In my experience Simple's main product is customer service (and delight). They're great at leveraging technology to accomplish this, but I'd say they're far from being a technology company.

In an ideal world I'm sure they would have created their app in-house, but it looks like outsourcing the development left them with a quality final product. Seems like a smart enough choice to me.

A co-worker in Mumbai also made some controversial statements on Facebook. He's absolutely fine, but just about every one of his friends scolded him for being so brazen. I was out of the city for the weekend, but by all accounts it was a terrible place to be.

This news is not terribly surprising, though as many have said, likely not true. It is extremely indicative of the immense gap between India and more developed nations.

I think you're missing the point. The idea is to provide incremental knowledge about the validity of the address, both to the user and to the service. user@existing.dns will validate but user@exsiting.dns won't. There is real value in providing that feedback immediately, rather than forcing the user to realize after waiting for an email that will never arrive that they made a trivial mistake.

To be clear, I agree with you 100% that there is no substitute for sending a confirmation email and requiring the user to click-through if you're looking for full confirmation of mailbox validity. My point is that there are simple steps to be taken along that path which complement the confirmation email.

Magic Memcached 15 years ago

You're absolutely right, it's a pretty awful layout for displaying code. I've been meaning to fix it for a while, just haven't gotten around to it. Thanks for stopping by though!