That's sometimes true, but I think (like mentioned in the article) a combo of a knowledge base with clear ways to contact a human usually leaves a good taste in my mouth.
We use Django REST and an angular frontend. Django is hosted on heroku, and angular is hosted on netlify. Netlify makes it super easy to proxy API requests from the front-end to our API backend.
That's really interesting and definitely something worth trying. I wonder how the effectiveness of email changes with the goals for the user (play solitaire vs pay for a subscription, etc).
Our startup uses a combo of Google Analytics, Stripe, and our own database for important metrics. Any plans to be able to pull directly from databases (we use postgres)? Thanks, seems like a cool product.
Just wanted to say that even though you said you're not a native English speaker, I never would have known if you hadn't mentioned it. Very well-written and clearly organized post.
I take the article to be written in the mindset he had at the time. When he made that quote you mentioned, he thought as he was heads-down building the product that it would be useful to those people.
He then goes on to describe the evidence specifically why doctor's DIDN'T want it. All the author was trying to do with that quote was explain what he was thinking at the time.
Couldn't agree more. The first interview is usually with a non-technical person (like HR), so at the first round candidates are often rejected for things that have no real bearing on job performance.