School Story:
I am a nitpicker; I am prone to notice and comment on small flaws in people's writings. For that matter I am sometimes supine I actually developed that aspect of my attention even before it stood me in good stead as a working programmer. We primates often pick louse eggs, nits, from each other's fur as a way of paying friendly attention to a neighbor. My own version is somewhat more metaphorical.
I'm 73 this year and haven't been programming much since about 1996. I had then spent thirty years at UCSF helping students, professors, and research staff use the computer center machines to get their work done. I became the person who explained error messages to programmers and the guy who reported flaws in compilers and other vendor supplied software to IBM and other vendors. That fostered my attention to detail.
After being laid off there, I looked around for something useful to do and found Jef Raskin. He's the guy who started the Macintosh project at Apple, but also wrote the amazing book about human interface issues, The Humane Interface. I actually helped him finish the book, and learned a lot in the process. Now I hope to learn how to do work in the modern, largely World Wide Web centric world.
If I succeed in that, perhaps I can demonstrate a better way to accumulate comments to a web page or blog posting by providing a relatively easy way to move them into an argumentation system so that readers can find the parts that interest them and can extend the discussion themselves. What I have in mind is a system based on IBIS, the Issue Based Information System. One feature of that is that before you can insert an idea, also known as a position or a claim, you must show the question to which your statement is an answer. Turns out that knowing the question clarifies the answer. Jeff Conklin of CogNexus.com wrote "Dialogue Mapping" which discusses this approach in some detail. He has some introductory YouTube videos on the subject which are easy to find.
Whatever I say, I hope to encourage feedback, especially feedback intended to change my opinion. Sometimes it does. We could talk about it. Here are some small issues with the usual forum or comment mechanism:
a. How can I most conveniently proceed to read the "next" forum or even the "next" forum entry?
b. Will I be able to correct or repair what I write, or not? How can I tell?
c. How about a link to wiki and FAQ or user manual?
d. Can we have a FEEDBACK button on every web page?
What if the FEEDBACK button opened a window on the same page, instantly, with the Message box FIRST and ready to type into. Then one would not be distracted from one's thought by waiting for a page to load, or by having first to fill in routine demographic information. It's not that hard to arrange if you take care one time and build it into the page skeletons in the first place. I'm happy to review documents and software in nitpicking detail if you like. Some authors appreciate the service. (Publish the result so other people can use on their web pages.)