Should I re-write old Article or Post New Article?
-
I have an article I wrote years ago, Painting Your Own Tabs[^] which has quite a following, with fixes posted by users etc, so I don't want to kill off the thread. However, I have since rewritten the code from the ground up, much better, fixing bugs and adding new functionality. My choices are: 1. Totally, re-write my original article, for the revised code. 2. Add all the revised code change details as a new section at the bottom (or top?) of the article. With the revised code, additional pictures, new coding tips, etc. 3. Post a new article, and change the old one to link to The new Version. What is the recommend practice?
If you have knowledge, let others light their candles at it. Margaret Fuller (1810 - 1850) [My Articles] [My Website]
-
I have an article I wrote years ago, Painting Your Own Tabs[^] which has quite a following, with fixes posted by users etc, so I don't want to kill off the thread. However, I have since rewritten the code from the ground up, much better, fixing bugs and adding new functionality. My choices are: 1. Totally, re-write my original article, for the revised code. 2. Add all the revised code change details as a new section at the bottom (or top?) of the article. With the revised code, additional pictures, new coding tips, etc. 3. Post a new article, and change the old one to link to The new Version. What is the recommend practice?
If you have knowledge, let others light their candles at it. Margaret Fuller (1810 - 1850) [My Articles] [My Website]
If I had an article that would need a serious rewrite (say over 30% gets changed), then I would: - create a new article, - choose a similar/same title and add "take 2", "reworked", "revisited", or so to it - copy all existing material that is still useful into it (maybe add a "copied" note to each chapter), - add/modify whatever needs being changed (maybe add a "new"/"modified" note to each new chapter), - start the introduction with "this is a extended and reworked version of my old article [here]" - add acknowledgments to all people who made helpful comments on the original article. And on the existing, old article I would add a "a newer article is available [here]" note in the introduction, and a similar message in its forum. Doing it that way, nobody is forced to read both articles to understand the current situation, and nobody will accidentally read the old one without being aware of the newer one. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use < PRE > tags for code snippets, it preserves indentation, and improves readability.
-
If I had an article that would need a serious rewrite (say over 30% gets changed), then I would: - create a new article, - choose a similar/same title and add "take 2", "reworked", "revisited", or so to it - copy all existing material that is still useful into it (maybe add a "copied" note to each chapter), - add/modify whatever needs being changed (maybe add a "new"/"modified" note to each new chapter), - start the introduction with "this is a extended and reworked version of my old article [here]" - add acknowledgments to all people who made helpful comments on the original article. And on the existing, old article I would add a "a newer article is available [here]" note in the introduction, and a similar message in its forum. Doing it that way, nobody is forced to read both articles to understand the current situation, and nobody will accidentally read the old one without being aware of the newer one. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use < PRE > tags for code snippets, it preserves indentation, and improves readability.
Thanks Luc. Time to get my article writing hat out.
If you have knowledge, let others light their candles at it. Margaret Fuller (1810 - 1850) [My Articles] [My Website]