Article Writing

Rick_Bishop wrote:

This system needs improving.

M.D.V.

If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.

1. Don't just give us a code dump. A good article explains the way you thought about the problem. It really helps us, as readers, if we can get a real understanding of what you were thinking when you wrote your code. Tell us why you chose to solve it in a particular way; what you chose not to do and why.
2. When you have completed your article, don't publish it straightaway. Instead, reach out to Sean Ewington at Code Project and request Mentor help. Mentors review articles before they reach the publish stage and can help you avoid having your code rejected out of hand.
3. Be original. I don't mean that you have to have a completely new idea that no one has thought of before. What I mean, instead, is that you should use your own words only; there must be no plagiarism.