> For example, in the story about the Japanese, he assumes some context from the reader: "What are they building? What is Fujitsu and what is Habitat and why does Japan need their own special version of it?" It's not even clear they're building anything technical, so I wondered, "Why do they need a client and server? And also, didn't you ever think to check their internal technical details before? What did you think would be the result?"
None of those details are important to the story. Leaving out extraneous detail is good communication.
None of those details are important to the story. Leaving out extraneous detail is good communication.