Yeah. This. We hackers should remember that the stuff we write, be it code, docs, proposals, business plans, security incident postmortems, whatever, needs to b

Yeah. This. We hackers should remember that the stuff we write, be it code, docs, proposals, business plans, security incident postmortems, whatever, needs to be VALUABLE to the readers -- the people -- we intend to reach. If it isn't valuable, they won't read or use it. If they don't read or use it, we've just wasted a lot of our time, and a little bit of theirs. Ouch. We're not trying to show people what WE think about anything. We're trying to influence how THEY think. This is tricky with code, because many members of our audience are future developers with less experience than us. Our brilliance is worthless to them. What's valuable to them is the ability to modify or built on what we did to solve their problems, problems we didn't forsee. Ask: what do our readers / users need to know / do? How can we convince them we CAN help them? Only THEN do we get to try to help them.