Writing "Micro" Articles?
-
I've been thinking about writing a few more articles for CP, but the problem is that I can't seem to find enough time to write full-length articles. Given my time constraints, I only have enough time to write articles that are two to three pages long. The articles aren't short enough to be just code snippets, and they might not be long enough to get past a "2" or "3" rating. So anyway, my question is this: should I just wait and clump everything together into one big article, or would writing these "micro" articles be a sound strategy? p.s. I could just post these articles on my blog, but I doubt it will get nearly the same amount of exposure as a CP publication. Anyway, what do you guys think?
Do you know...LinFu?
-
I've been thinking about writing a few more articles for CP, but the problem is that I can't seem to find enough time to write full-length articles. Given my time constraints, I only have enough time to write articles that are two to three pages long. The articles aren't short enough to be just code snippets, and they might not be long enough to get past a "2" or "3" rating. So anyway, my question is this: should I just wait and clump everything together into one big article, or would writing these "micro" articles be a sound strategy? p.s. I could just post these articles on my blog, but I doubt it will get nearly the same amount of exposure as a CP publication. Anyway, what do you guys think?
Do you know...LinFu?
Philip Laureano wrote:
Anyway, what do you guys think?
Go ahead and write them. I would make sure to get the additional articles up a short while after posting so it doesn't keep people waiting.
Philip Laureano wrote:
they might not be long enough to get past a "2" or "3" rating.
Depends on the content. I've seen short articles with powerful content fetch very respectable ratings.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
-
I've been thinking about writing a few more articles for CP, but the problem is that I can't seem to find enough time to write full-length articles. Given my time constraints, I only have enough time to write articles that are two to three pages long. The articles aren't short enough to be just code snippets, and they might not be long enough to get past a "2" or "3" rating. So anyway, my question is this: should I just wait and clump everything together into one big article, or would writing these "micro" articles be a sound strategy? p.s. I could just post these articles on my blog, but I doubt it will get nearly the same amount of exposure as a CP publication. Anyway, what do you guys think?
Do you know...LinFu?
I would much rather have a very short, explanatory and stimulating article than lots of code and examples. Hope I haven't set the bar too high. :~
-
I've been thinking about writing a few more articles for CP, but the problem is that I can't seem to find enough time to write full-length articles. Given my time constraints, I only have enough time to write articles that are two to three pages long. The articles aren't short enough to be just code snippets, and they might not be long enough to get past a "2" or "3" rating. So anyway, my question is this: should I just wait and clump everything together into one big article, or would writing these "micro" articles be a sound strategy? p.s. I could just post these articles on my blog, but I doubt it will get nearly the same amount of exposure as a CP publication. Anyway, what do you guys think?
Do you know...LinFu?
Do it, My preference is for articles that discuss one point and do it very well. If they happen to be short and concise then that's even better.
I just love Koalas - they go great with Bacon.
-
I've been thinking about writing a few more articles for CP, but the problem is that I can't seem to find enough time to write full-length articles. Given my time constraints, I only have enough time to write articles that are two to three pages long. The articles aren't short enough to be just code snippets, and they might not be long enough to get past a "2" or "3" rating. So anyway, my question is this: should I just wait and clump everything together into one big article, or would writing these "micro" articles be a sound strategy? p.s. I could just post these articles on my blog, but I doubt it will get nearly the same amount of exposure as a CP publication. Anyway, what do you guys think?
Do you know...LinFu?
Have you seen some of the articles put forward X|. I don't think size matters (couldn't resist) it's the content. I actually prefer a short pithy article. I have seen many small article get the nod so please, go ahead and write your mini articles.
Never underestimate the power of human stupidity RAH
-
I've been thinking about writing a few more articles for CP, but the problem is that I can't seem to find enough time to write full-length articles. Given my time constraints, I only have enough time to write articles that are two to three pages long. The articles aren't short enough to be just code snippets, and they might not be long enough to get past a "2" or "3" rating. So anyway, my question is this: should I just wait and clump everything together into one big article, or would writing these "micro" articles be a sound strategy? p.s. I could just post these articles on my blog, but I doubt it will get nearly the same amount of exposure as a CP publication. Anyway, what do you guys think?
Do you know...LinFu?
Philip Laureano wrote:
two to three pages
That doesn't sound short to me. You wanna see short? I'll show you short! :~ Most articles on here are far too long.
-
I've been thinking about writing a few more articles for CP, but the problem is that I can't seem to find enough time to write full-length articles. Given my time constraints, I only have enough time to write articles that are two to three pages long. The articles aren't short enough to be just code snippets, and they might not be long enough to get past a "2" or "3" rating. So anyway, my question is this: should I just wait and clump everything together into one big article, or would writing these "micro" articles be a sound strategy? p.s. I could just post these articles on my blog, but I doubt it will get nearly the same amount of exposure as a CP publication. Anyway, what do you guys think?
Do you know...LinFu?
I agree that there have been a rash of "articles" that are nothing more than blogs regurgitated. We've also seen two lines of code snipped as an "article." If it's sweet, to the point and you really show why it's good/better, etc. I'm all for short articles.
Blog link to be reinstated at a later date.
-
I've been thinking about writing a few more articles for CP, but the problem is that I can't seem to find enough time to write full-length articles. Given my time constraints, I only have enough time to write articles that are two to three pages long. The articles aren't short enough to be just code snippets, and they might not be long enough to get past a "2" or "3" rating. So anyway, my question is this: should I just wait and clump everything together into one big article, or would writing these "micro" articles be a sound strategy? p.s. I could just post these articles on my blog, but I doubt it will get nearly the same amount of exposure as a CP publication. Anyway, what do you guys think?
Do you know...LinFu?
Hi Philip, This thread, for me, dovetails with a recent discussion prompted by our very own "outlaw-legend in his own mind" John Simmons's posting of an article that was essentially a relatively smaller collection of a few excellent tips/techniques. I and others responded we saw a need for a slightly different kind of article-archive repository for short(er) articles. And Chris M. responded that CP was working on this idea, already. While I agree with other posters here that an article's length is less important than its utility, its technical excellence, and its creativity, how can you fairly rate an article that is shorter, more limited in scope, compared to such "magnum opii" as the veritable epics penned by luminaries like Clifton, Barber, and others ? And once again I notice how much easier it is to think about what CP should do than to think about writing an article for CP :) best, Bill
"The greater the social and cultural distances between people, the more magical the light that can spring from their contact." Milan Kundera in Testaments Trahis
-
I've been thinking about writing a few more articles for CP, but the problem is that I can't seem to find enough time to write full-length articles. Given my time constraints, I only have enough time to write articles that are two to three pages long. The articles aren't short enough to be just code snippets, and they might not be long enough to get past a "2" or "3" rating. So anyway, my question is this: should I just wait and clump everything together into one big article, or would writing these "micro" articles be a sound strategy? p.s. I could just post these articles on my blog, but I doubt it will get nearly the same amount of exposure as a CP publication. Anyway, what do you guys think?
Do you know...LinFu?
If ratings are essentially what you priortize, then your decision all depends on how useful each specific article is. I think that coders first and foremost rate an article based on its usefulness...if they finish reading it, of course--which is highly probable. So don't get me wrong, ratings are extremely important, since they basically denote how much and how many people you helped. My point is that the perceived usefulness (and therefore the article rating) is much more important than article length. Don't let conciseness get in the way of sharing valuable information to others :)
-
I've been thinking about writing a few more articles for CP, but the problem is that I can't seem to find enough time to write full-length articles. Given my time constraints, I only have enough time to write articles that are two to three pages long. The articles aren't short enough to be just code snippets, and they might not be long enough to get past a "2" or "3" rating. So anyway, my question is this: should I just wait and clump everything together into one big article, or would writing these "micro" articles be a sound strategy? p.s. I could just post these articles on my blog, but I doubt it will get nearly the same amount of exposure as a CP publication. Anyway, what do you guys think?
Do you know...LinFu?
Go for it. Short and to the point articles get a reader an answer to their problem quickly. Just make sure you include a download that builds and runs - not doing that is guaranteed to get a few people's backs up.
-
I've been thinking about writing a few more articles for CP, but the problem is that I can't seem to find enough time to write full-length articles. Given my time constraints, I only have enough time to write articles that are two to three pages long. The articles aren't short enough to be just code snippets, and they might not be long enough to get past a "2" or "3" rating. So anyway, my question is this: should I just wait and clump everything together into one big article, or would writing these "micro" articles be a sound strategy? p.s. I could just post these articles on my blog, but I doubt it will get nearly the same amount of exposure as a CP publication. Anyway, what do you guys think?
Do you know...LinFu?
I prefer shorter articles, longer ones by their nature are generally focussed on big task - and that task is rarely obviously transportable. I much prefer bite-size articles, digestible in a lunch-time. Tips and tricks are good; as are 'building block' articles that takes a small area and nails it - enabling that knowledge to be used as part of a bigger project. I've always been put off writing articles because of the perceived size issue and some of the trolls who look to criticize every minor point.
"If you reward everyone, there will not be enough to go around, so you offer a reward to one in order to encourage everyone." Mei Yaochen in the 'Doing Battle' section of Sun Tzu's: Art of War. .
-
I've been thinking about writing a few more articles for CP, but the problem is that I can't seem to find enough time to write full-length articles. Given my time constraints, I only have enough time to write articles that are two to three pages long. The articles aren't short enough to be just code snippets, and they might not be long enough to get past a "2" or "3" rating. So anyway, my question is this: should I just wait and clump everything together into one big article, or would writing these "micro" articles be a sound strategy? p.s. I could just post these articles on my blog, but I doubt it will get nearly the same amount of exposure as a CP publication. Anyway, what do you guys think?
Do you know...LinFu?
A clearly-written useful article will always get a 5 from me.
Best wishes, Hans
[CodeProject Forum Guidelines] [How To Ask A Question] [My Articles]
-
Hi Philip, This thread, for me, dovetails with a recent discussion prompted by our very own "outlaw-legend in his own mind" John Simmons's posting of an article that was essentially a relatively smaller collection of a few excellent tips/techniques. I and others responded we saw a need for a slightly different kind of article-archive repository for short(er) articles. And Chris M. responded that CP was working on this idea, already. While I agree with other posters here that an article's length is less important than its utility, its technical excellence, and its creativity, how can you fairly rate an article that is shorter, more limited in scope, compared to such "magnum opii" as the veritable epics penned by luminaries like Clifton, Barber, and others ? And once again I notice how much easier it is to think about what CP should do than to think about writing an article for CP :) best, Bill
"The greater the social and cultural distances between people, the more magical the light that can spring from their contact." Milan Kundera in Testaments Trahis
BillWoodruff wrote:
outlaw-legend in his own mind" John Simmons
Hey, HEY! I *am* a legend. Just wait - years after I die, you guys will STILL be talking about me. In fact, I bet Chris creates a scholarship program in my name, or someone erects a statue of some sort, or the next great computer idea will be named after me. :)
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
I've been thinking about writing a few more articles for CP, but the problem is that I can't seem to find enough time to write full-length articles. Given my time constraints, I only have enough time to write articles that are two to three pages long. The articles aren't short enough to be just code snippets, and they might not be long enough to get past a "2" or "3" rating. So anyway, my question is this: should I just wait and clump everything together into one big article, or would writing these "micro" articles be a sound strategy? p.s. I could just post these articles on my blog, but I doubt it will get nearly the same amount of exposure as a CP publication. Anyway, what do you guys think?
Do you know...LinFu?
I've found that people want a sample application that uses your code. The problem is that to make the sample application even somewhat interesting, you have to apply the "real world" test to it. In other words, theory is nice, but how would you use your code in an honest-to-god application, and what issues might you face in doing so? Eventually (and more often than most folks realize), the article becomes more about the sample application than the technique itself. Case in point - my CodeProject Article Scraping article. Sometimes, it can't be helped. Whether or not an article is "full-length" is a subjective opinion. If the article completely describes the technique, it's "full-length". If you consider the discussion to be too long to be contained in a single article, by all means write a multi-part article, but if you do that, post all of the parts at the same time. Most of the time, people submit "Part 1 of n", and never get around to posting any further parts, leaving their readers hanging.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
I've been thinking about writing a few more articles for CP, but the problem is that I can't seem to find enough time to write full-length articles. Given my time constraints, I only have enough time to write articles that are two to three pages long. The articles aren't short enough to be just code snippets, and they might not be long enough to get past a "2" or "3" rating. So anyway, my question is this: should I just wait and clump everything together into one big article, or would writing these "micro" articles be a sound strategy? p.s. I could just post these articles on my blog, but I doubt it will get nearly the same amount of exposure as a CP publication. Anyway, what do you guys think?
Do you know...LinFu?
-
BillWoodruff wrote:
outlaw-legend in his own mind" John Simmons
Hey, HEY! I *am* a legend. Just wait - years after I die, you guys will STILL be talking about me. In fact, I bet Chris creates a scholarship program in my name, or someone erects a statue of some sort, or the next great computer idea will be named after me. :)
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001Excuse me while I access the John to process a load... :-D
-
I've found that people want a sample application that uses your code. The problem is that to make the sample application even somewhat interesting, you have to apply the "real world" test to it. In other words, theory is nice, but how would you use your code in an honest-to-god application, and what issues might you face in doing so? Eventually (and more often than most folks realize), the article becomes more about the sample application than the technique itself. Case in point - my CodeProject Article Scraping article. Sometimes, it can't be helped. Whether or not an article is "full-length" is a subjective opinion. If the article completely describes the technique, it's "full-length". If you consider the discussion to be too long to be contained in a single article, by all means write a multi-part article, but if you do that, post all of the parts at the same time. Most of the time, people submit "Part 1 of n", and never get around to posting any further parts, leaving their readers hanging.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001One must also keep in mind that if a fully working and useful application is included, some loser may turn around and try to sell it.
-
Excuse me while I access the John to process a load... :-D