2021-12-02 UTC
# 
Don A good technical document starts from a point of empathy: It identifies a problem the reader is already experiencing, and describes it in terms they already understand. Then it uses that shared context to lead them into what a solution looks like, and how to implement it (whether from scratch or using an existing service).