Hacker News Reader

I applied to IFTTT about a year ago (didn't get the job), part of the interview process was to develop a channel on their developer platform. I don't consider my self a fast developer but it wasn't difficult and it took me about a weekend of casual work. Maciej is well within his rights to flip IFTTT the bird, but I just wanted to provide some context about how much work is involved.

View on HN

I agree that implementing a simple API endpoint is easy.

Running that endpoint is not easy. Once it's live, you're dealing with an entangled system of API, user, network, database, server, full moon, voodoo curse, and God knows what else. It's a giant flaming tumbleweed of pain.

Clearly IFTTT agrees, and that's why they're trying to make us do it for them.

You're absolutely right. I will not try to compare what I did to pinboard. I still have the channel running on a DigitalOcean box and even though the service is simple and stable, I still have to fiddle with it once in a while. I only keep it running because it's valuable... to me.

Reply on news.ycombinator.com