Proposal: Technical Communication
I am not a tech writer, or any other form of documentation professional. I am a computer programmer. As I write programs I try to think of their documentation. Both internal to the code, for future maintainers, and external to it for the users of the finished product.
I have never heard of the many of tools, or other things, mentioned in the sample questions, such as DITA XML, SMEs, WriteGood, proselint, etc. I know how to make Perl programs generate documentation through Perldoc using markup in the source code, and that doing so is a standard in the Perl community. I haven't seen, though don't doubt that it exists, the same functionality for PHP, the other "current" language that I use. My other languages are likely to ancient to worry about.
OTOH: I am a user of documentation and have suffered from trying to find the information I needed in the documentation for things - computer-based and non-technical. For example, I've had the joy of assembling an out-of-the-box desk with the instructions using zero text, and line drawings that do not match the pieces in my hands.
I never will be a "professional" in technical communication. As my workflow changes, however, I expect to have an increasing need to do professional style documentation. I believe I can learn a lot from this site, and maybe even help it a little. I will have, as they say, "fresh eyes." Maybe I can even help to compensate for the "curse of knowledge" that @mbakeranalecta is worried about.
The bottom line here is:
- How much am I likely to be able to help the site?
- Is it helpful, or harmful, for me to commit to the site when it (soon) reaches that point?