This is a group for software developers/writers who are interested in feedback from peers and interacting with a thinking, mildly critical community. We cover all aspects of software development: requirements, coding, testing, implementation plan, design, security, and so on.

Members will post ideas for articles, requests for comments, completed articles, outlines, and so on, typically in advance of submission to a publisher or journal. Discretion in reading posts is very important; all intellectual property rights are assumed to be held unless explictly disavowed. Our focus is on articles that are relevant to industry, but there are no formal rules. For example, you could post comics, academic papers, or even code snippets if you think it would fit in the community.

Now, there are very few 'new' topics created, but typically the topic+slant combination is unique.

For example, let's say that author Bob writes an abstract about the challenges (slant) of using test-first development (topic) for web services (slant).

It would be bad form to pitch a similar idea to an editor; members of SW-Writing-Review offer a gentlemen's agreement to not do so without the original contributor's consent. Cutting and pasting the idea and sending it to an editor is just plain illegal.

If you join SW-Writing Review and ask others to review your work, please review the work of someone else between your requests for help. That's just polite.

If you have any additional questions, you can email me, the moderator, for more information. (Google me; I'm Matthew Heusser)