Original Post

Ironically, product managers designing project management software, lack an abstract skill of the thinking about time as a spatial dimension.

For decades, users suffer from the "live-offline" dualism incompetence in computer science.

While watching an old video, why not fast forward to the live source?

While entering a video conference after it's over, why not rewind it back to see what we've missed?

While going offline with a Google Doc, and after returning back, why not automatically create a conflict resolution UI, and propose a Pull Request to merge it by other collaborators?

Why new Microsoft's "Teams" is so slow when browsing between tabs? What about offline access?

Concurrent, offline, and collaborative hierarchical documents editing computer science theory went insanely beyond of our imagination. But an entire generation of product managers seem to be totally unaware about this theory and design their products like it's Web 1.0.

Software developers, thrown on modern projects, often lack knowledge of the theory of concurrent computing, and they even avoid to think about these scary concepts of conflicts resolution!

Modern software runs slow, because an entire generation of web developers has built a "perfect world", where everything is always consistent.