Long ago, when I was just starting to work as an information systems designer, I was tormented by the description problem: I couldn’t squeeze anything more than one or two sentences about the behavior of the interface. I could not and everything, even if you burst. Yes it is a button. Yes, it is. Yes, several states. And what? Dead stupor.
Having suffered this way for some time, I came to the conclusion that the problem is not that the interface is difficult to describe, but it is difficult for me to describe it. I found several articles in the network, telling about the formation of the writing style, the rules of narration, and I understood that all this helps me badly. Well, not really bad at all, but it was obviously not worth spending a week on it, because the problem was not just writing style, but inertness of thinking.
I decided to act "brute force". On cold winter evenings, he poured a large cup of hot tea and sat down to write essays on various topics: “the sharp steps are fine”, “the seasons and the thickness of dust under the bed”, “the monitor color and the passive behavior of ants during the mating season of ground beetles”. The general principle of the selection of themes is: the more absurd - the better. But at the same time, it is necessary to understand that an ordinary translation of the brain flow will not work, it is important that this is an essay on a given topic.
')
At the same time, when I came to work, I allocated about an hour to review the “web-news” and to create a consolidated report highlighting features important to our company, which was sent to the general newsletter to colleagues around the office and developed into the knowledge base. Colleagues, probably, still do not know why I did it.
After some time (about two or three months of classes), I learned to write on any topic for as long as required and in any detail.