to write or not to write an article

Question

5.00/5 (4 votes)

See more: (untagged)

An article about sensible data (using MFC), would it be interesting to someone?... or about CRichEditCtrl (also using MFC), might it be useful?

Posted 9-Nov-08 11:29am

aljodav

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

Pete O'Hanlon · Answer 1 · 2008-11-09T22:47:00

Solution 1

Write the articles. Even if it's not relevant to what I'm doing on a day to day basis, I do enjoy a well written article and will read it.

Posted 9-Nov-08 22:47pm

Pete O'Hanlon

Paul Conrad · Answer 2 · 2008-11-10T17:30:00

Solution 2

Do write the article, like Pete has mentioned. It may not be useful for my day-to-day programming purposes, but sounds like something I would find worth reading and other members of this site may find it useful, too. :)

Posted 10-Nov-08 17:30pm

Paul Conrad

Scott Dorman · Answer 3 · 2008-11-11T03:28:00

Solution 3

Definately write the article. There will almost always be someone else who is running in to (or will run in to) a problem the article will help to solve.

Posted 11-Nov-08 3:28am

Scott Dorman