Sounds like everyone just kept on going like they were in person. Remote work takes a different cadence and communication patterns. I work at a 100% remote company and we have none of those problems (AFAIK).
- We use email extensively, both person-to-person and with various internal mailing lists we can subscribe to.
- Slack is very asynchronous and it is common for people to silence it when busy.
- All meetings are recorded and optional if you aren't an active participant.
- We write everything down with historical archives, for example all projects are proceeded by a written RFC describing the problem, solution and alternatives.
I disagree. C is also an abstraction of reality over assembly, assembly is an abstraction over machine code, which abstracts microcode, which abstracts over logic gates, and there are both deeper and adjacent abstractions as well. Underlying it all are different mathematical abstractions from karnaugh maps to quantum physics.
A good developer will IMO select an abstraction that best matches their goals. If you’re writing a device driver then the abstraction might be assembly language. If you’re writing business logic it might be PL/pgSQL. But regardless of which abstraction you choose, you’re hiding something from someone.
- We use email extensively, both person-to-person and with various internal mailing lists we can subscribe to.
- Slack is very asynchronous and it is common for people to silence it when busy.
- All meetings are recorded and optional if you aren't an active participant.
- We write everything down with historical archives, for example all projects are proceeded by a written RFC describing the problem, solution and alternatives.
There are places that do remote work well.