Personally, I hate Pinterest with a passion, mainly because of how it pollutes image searches with useless, context-less results.

I have to do -site searches for certain types of image searches. OTOH that does fix this issue pretty easily.

Pinterest founders are business+design. Therefore the company is not engineering first, it's product and design first.

This is why it's not particularly loved on HN, and this is also why the tech stack is nothing special (it's not bad, it's just not special).

What is special is the unbelievable product market fit. Engaged Pinterest users 1) spend a shitton of time on the app (hours a day) and 2) interact very positively with ads (this is VERY purposeful and part of the product first company style).

I think their recipe makes for a great company, but it's not the most fun for engineers to work on (those things don't always if ever correlate).

They were very early adopters of Elixir!

They do? They should actually talk about it on their tech blog (https://medium.com/@Pinterest_Engineering). I couldn't find it other then third party post talking about them using it (https://prograils.com/posts/why-discord-pinterest-moz-bleach...).

Even their github https://github.com/pinterest, elixir isn't even in their top programming languages.

It could be the secret sauce language kind of deal. Or they've moved away from it.

It is a pleasure to see you outside of elixirforum.

Thanks! I'm glad I could get the same handle.

AFAIK, Pinterest rewrote the logic of their notification system into Elixir and also used it to rebuild their rate limiter.

This is the main piece I've seen open sourced: https://github.com/pinterest/elixir-thrift