Hacker News new | ask | show | jobs
by mfuzzey 1336 days ago
I think it's far better give the reader as much information as reasonable and let him decicde how much he wants / needs to read. That can avoid multiple round trips and makes sure the whole picture is available to anyone who may need it.

Particularly as often the same message will be sent to multiple recieients that have different needs.

Of course you should try to structure the message so that people don't necessarilly have to read all of it.

For instance I recently sent a message about an analysis of the feasibility of changing a piece of hardware to a group that contained

* Managers * Hardware developers (in charge of implementing the hardware modification) * Software developers (in charge of adapting the software to the new hardware)

So it started with a brief summary of the idea and conclusion "yes it will work" (for the managers).

Continued with a some comments, questions addressed to the hardware team "the aproach is fine but we still need to sort out X,Y,Z"

And finished with a detailed description for the software team of how we should integrate the new hardware whilst remaining compatible with the existing.