How remote work is done at my company: Don't go async! -- details of my ~9-mo remote experience.

There's abundant advice on the web that to do remote, you must go asynchronous, writing-heavy. My opinion: *You don't have to*, fails more. This article outlines my ~8-9mo of remote experience and a couple-of-years' team experience. For **office**-like teams.

Framer — Launch websites with enterprise needs at startup speeds.

Launch websites with enterprise needs at startup speeds.

I've had a short, painful experience with remote when I once tried to go asynchronous, as most advice on the web says. Working at the company I'm working with now has changed my view of remote: It can be for normal, verbal-communication-based teams as well! ... Just simulate office work with the cool tools of Slack & Zoom. I wish someone had written this before I started remote: how it can be done when asynchronous work is not suitable for the team members, use-case, or whatever other reason. The article itself is on Gumroad: https://gumroad.com/l/fatcPp A nice intro to it: https://dev.to/hossameldeen/let-... If anyone can't afford: https://forms.gle/2rdCPu5NLDFTTAf3A Disclaimer: Not of the highest quality .. but describes my to-the-point experience of how remote is done at my company -- in a real-time, office-like way.

Framer — Launch websites with enterprise needs at startup speeds.

Launch websites with enterprise needs at startup speeds.