My somewhat reductive conclusion about remote work is that it boils down to the ability to be an effective writer.
If you're not good at written communication, or you work with people who are not good at it, remote work will be miserable.
People who are not highly fluent in the company's written language or those with some level of dyslexia will struggle. Also some people get frustrated with the more analytic approach required by text, relying instead on spoken rhetoric.
I think even if you're colocated, there are huge benefits to following the remote work practices and improving your written communication. Documenting your work in an issue manager and using chat primarily for communication means no one will miss out, even if someone is sick, a new starter, or on a different team. All these things can make a dev organisation much more effective and break down silos.
If you're not good at written communication, or you work with people who are not good at it, remote work will be miserable.
People who are not highly fluent in the company's written language or those with some level of dyslexia will struggle. Also some people get frustrated with the more analytic approach required by text, relying instead on spoken rhetoric.
I think even if you're colocated, there are huge benefits to following the remote work practices and improving your written communication. Documenting your work in an issue manager and using chat primarily for communication means no one will miss out, even if someone is sick, a new starter, or on a different team. All these things can make a dev organisation much more effective and break down silos.