robby_w_g

Prior discussion can be found here: https://news.ycombinator.com/item?id=26724237

The CEO has posts in the thread as well.

> I bag on Amazon a lot on here (which if I were to review with my therapist is likely because I had an absolutely HORRENDOUS experience in an interview loop with them my first step out of college that still makes me nervous in interviews, even 15 years later).

Hey, I had a similar experience with Google! It was my first technical interview for my first job out of college. The interviewer laughed at my code, and then after going through the logic said "Wow I can't believe this actually works."

Personal grievances aside, I've come to think that the Leetcode interview style has morphed from a "let's see how you handle problems at scale" test into an ego-driven hazing ritual. My biggest gripe is that Leetcode is systematically favoring candidates who have months of free time to memorize arbitrary logic puzzles. It makes me sad for the less privileged candidates who might be working a job while also trying to break into the IT field.

> I imagine this will get them in some sort of trouble.

I'm not sure about this.

I bet Google is happy to collect the text data of up to 500 million users with zero restrictions from Telegram's end on how the data is used. I'm not a lawyer, but my hunch is that Google's data privacy policy applies to the official, premium service: https://cloud.google.com/terms/data-processing-terms

Google might make the determination that they'll get more value from allowing Telegram to abuse the unofficial API. However, they might face some angry customers who are paying a premium to use the official API now that this loophole has been published.

> But, again, if you're also annoyed that social story telling IRL happens with interruptions and digressions and background noise

Really, this pub/Twitter comparison doesn't work. Yes, interruptions happen IRL, but they aren't systematically happening every other sentence. Also, you can use body language or talk louder to ensure you're understood IRL. Internet communication doesn't have the same luxury.

Disruption while consuming information in the browser is a different animal compared to person-to-person contact.

> Its like saying 'I wish he hadn't told they story down the pub, the pub is a terrible place to tell stories as it is too noisy and I find it hard to follow with everything else going on'.

More like 'I wish he hadn't told the story at the pub in small snippets over 4-6 drinks'

Twitter, unlike pubs, has intentional systems in place to interrupt medium to long-form communication. It was designed to be a bad medium for telling stories, so chaining a dozen tweets is a frustrating experience for both the author and the reader.

It's obvious why people still insist on using Twitter for telling stories: Twitter is a massively popular website, and the author will lose some percentage of readership if they link to an external blog. Ideally, Twitter would recognize that this is now a major use case and would add UI to support long-form communication. In the meantime, it'd be nice if people shared Twitter chains via threadreaderapp or authors used screenshots of the Notes app. Using a medium designed for telling stories would be even better.