Remote to my grandmother is what she uses to change channel. To us is a way of life. It means different things to different people. There's no appropriation being done here, nor do we plan to do so. We fundamentally respect what it means to be remote and we're only a way to improve it and make it more mainstream, nothing more.
Everything we do professionally can be a recipe for burnout. We also have strong policies to prevent it but that's another topic altogether.
A "short-ish" article written in an afternoon has no hopes of being a tablet of truth, just some anecdotal examples and ideas I've experienced over the years.
I fundamentally agree with the "Be human..." part, that's all you need if common sense is common around your workplace. Unfortunately it often isn't and you need to offset the unbalance to find equilibrium.
Ah ah! I did and I do. That's why well written documentation is more than a "good to have", it's as important as the code itself, same as good tests.
Communication is always a challenge and no big or small company has fully cracked it for sure. Average engineers - whatever that means - need training and meaningful tutoring. The team should aim at becoming better, not settle for whatever they have at the moment.
I've been a manager of different teams for a while now and I must admit that every form of management or productivity strategy is nothing but written nonsense in good form - or common sense in fancy terms.
Async work is but a tool, a methodology, remote is a way of life/work. I advocated async work when working office-based as well, the same principles still apply.
Love that you feel so passionate about it! We are part of that community, and we're doing this so that more people can enjoy working remotely as well. It changed my life in many positive ways and there's nothing we want to take away from it, quite the opposite. We own the domain, we don't own something that is a way of life for which we have tremendous respect.