Andreas Thaler
Subscriber
Once again I am thinking about my repair reports here and how I can best write them.
I am trying to put myself in the position of two fictitious readers:
For one, it is too dense and too long, for the other, too reduced.
Feedback gained
I noticed that when I started my repair reports in November last year, I received a lot of feedback, resulting in interesting discussions, which then decreased over time.
Apparently, my readers were initially still willing to read longer texts. Or the reports had a density and length that was acceptable to everyone.
This shows me that I need to change something here.
Views as a guide
I can tell whether my reports are popular by the views indicated in the forum topic overview. These should be internal and external readers who find my articles via Google, for example.
From this I try to get an idea of which reports are of interest and which are less so. Are these longer or shorter articles, or ones on specific topics?
Since I am always learning new things myself, the information I want to convey is also increasing.
Splitting reports
I will therefore now split my reports into two independent parts:
I am curious to see how this will be received
I am trying to put myself in the position of two fictitious readers:
- Reader A wants concise and easy-to-read information on how to solve a problem. He is less interested in details and background than in a quick way to solve the problem, preferably as a tutorial.
- Reader B is more interested in analyzing the problem and the details of how to solve it. In return, he is prepared to read longer texts.
For one, it is too dense and too long, for the other, too reduced.
Feedback gained
I noticed that when I started my repair reports in November last year, I received a lot of feedback, resulting in interesting discussions, which then decreased over time.
Apparently, my readers were initially still willing to read longer texts. Or the reports had a density and length that was acceptable to everyone.
This shows me that I need to change something here.
Views as a guide
I can tell whether my reports are popular by the views indicated in the forum topic overview. These should be internal and external readers who find my articles via Google, for example.
From this I try to get an idea of which reports are of interest and which are less so. Are these longer or shorter articles, or ones on specific topics?
Since I am always learning new things myself, the information I want to convey is also increasing.
Splitting reports
I will therefore now split my reports into two independent parts:
- the problem description and analysis will be the first post and
- the attempt to solve the problem will be the second post.
I am curious to see how this will be received

Last edited: