This is really just advertising (little content in the slides) for Slite [0].

Looks at a brief glance that it might be interesting, probably a better URL for the submission than the current slide deck [1].

In fact, @clmntrg, from your submission history I gather Slite is yours (a few submissions about it on blogs/reddit) - why not 'Show HN: Slite - the workspace for async teams' (slite.com link)? I'm sure it would be better received than these 'pitch.com' slides. [2]

[0] - https://slite.com

[1] - (in case it is updated) https://app.pitch.com/app/public/player/5fa67ab4-b618-46dd-a...

[2] - (examples in case you don't know what I mean) https://news.ycombinator.com/show

Hey, thanks for taking the time to leave feedback on the post – harsh but I'll take it. I wanted to figure out a way to TLDR a blog piece we wrote about what profiles fit best in async environments, from our won experience. Seems like the format doesn't work well, I'll pass that to the team. Have a great day

I cringed so hard looking through this. What's wrong with people?

This is a low effort comment, but I agree. Who does this appeal to? Managers?

Remote workers looking for a job, or managers in a remote company.

While working at a company that builds an alternative to meetings, calls and office-friendly practices, I had lots of questions about "would this work for me?". Or people were saying "async seems promising, but I'm sure it's only for developers". This is untrue.

I take the design is not your taste, I'll pass this feedback to the team. Thanks Dimgl

I thought this was building up to: here is who it's NOT good for and how to help them.

But it doesn't. It just says it's great for everyone. Which it obviously isn't... It's good for some, horrible for others.

I was also disappointed by this overly simplistic and cheerful view.

Async communication, like most things, isn't equally well-suited to all scenarios (never mind people).

I worked in a primarily async environment and while I, as an individual, like many aspects of this manner of work it is sometimes a terribly inefficient way to get things done. In some instances a meeting with a handful of people can save you weeks of back and forth on Slack, each time with a bunch of context switching.

Please read again, it doesn't work for everyone. The TLDR from our own experience is that it's hard to make it work for juniors.

I guess they mean async communication between humans, not async as in the JS / C# / Rust language feature?