Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Other Discussions
  3. The Back Room
  4. Posting Articles vs. Projects

Posting Articles vs. Projects

Scheduled Pinned Locked Moved The Back Room
helpquestioncssvisual-studiocollaboration
3 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • U Offline
    U Offline
    unitrunker
    wrote on last edited by
    #1

    I'm seeing some articles that over a period of months and years have evolved into ongoing projects. The purpose of an article is to describe a specific technique, approach or solution to a problem. Except for corrections and minor revisions - it is fairly static in content and will eventually become obsolete over (a possibly long) time. A project is a complete working program or library. The article text is more or less a "how-to" of how to use the program or library. As the code improves, the article text must be revised to correctly reflect new behavior. The article becomes a living document where any draft is a snapshot in time of where the project stood in its evolution. My question - is posting a project style article on CodeProject a good thing? Might some of the project-articles fair better somewhere like SourceForge? One main benefit of SF is visibility of source revisions - including the article text - via the CVS or SVN repository feature of that site. I seeing some of the same articles pop up over and over again. I can't tell if they are minor typo fixes, minor bug fixes, or contain significant new content (ie. is the article worth re-reading?). I can easily see the value of a "how to" article that links to an SF hosted project. :rose: Ideas?

    J V 2 Replies Last reply
    0
    • U unitrunker

      I'm seeing some articles that over a period of months and years have evolved into ongoing projects. The purpose of an article is to describe a specific technique, approach or solution to a problem. Except for corrections and minor revisions - it is fairly static in content and will eventually become obsolete over (a possibly long) time. A project is a complete working program or library. The article text is more or less a "how-to" of how to use the program or library. As the code improves, the article text must be revised to correctly reflect new behavior. The article becomes a living document where any draft is a snapshot in time of where the project stood in its evolution. My question - is posting a project style article on CodeProject a good thing? Might some of the project-articles fair better somewhere like SourceForge? One main benefit of SF is visibility of source revisions - including the article text - via the CVS or SVN repository feature of that site. I seeing some of the same articles pop up over and over again. I can't tell if they are minor typo fixes, minor bug fixes, or contain significant new content (ie. is the article worth re-reading?). I can easily see the value of a "how to" article that links to an SF hosted project. :rose: Ideas?

      J Offline
      J Offline
      Jorgen Sigvardsson
      wrote on last edited by
      #2

      You should probably post this in the lounge, as it would get more attention. This is the bullshit forum...

      -- Kein Mitleid Für Die Mehrheit

      1 Reply Last reply
      0
      • U unitrunker

        I'm seeing some articles that over a period of months and years have evolved into ongoing projects. The purpose of an article is to describe a specific technique, approach or solution to a problem. Except for corrections and minor revisions - it is fairly static in content and will eventually become obsolete over (a possibly long) time. A project is a complete working program or library. The article text is more or less a "how-to" of how to use the program or library. As the code improves, the article text must be revised to correctly reflect new behavior. The article becomes a living document where any draft is a snapshot in time of where the project stood in its evolution. My question - is posting a project style article on CodeProject a good thing? Might some of the project-articles fair better somewhere like SourceForge? One main benefit of SF is visibility of source revisions - including the article text - via the CVS or SVN repository feature of that site. I seeing some of the same articles pop up over and over again. I can't tell if they are minor typo fixes, minor bug fixes, or contain significant new content (ie. is the article worth re-reading?). I can easily see the value of a "how to" article that links to an SF hosted project. :rose: Ideas?

        V Offline
        V Offline
        Vasudevan Deepak Kumar
        wrote on last edited by
        #3

        This is a soft discussion and hence befits Lounge rather than Soapbox which is targetted at aggressive debating.

        Vasudevan Deepak Kumar Personal Homepage
        Tech Gossips
        A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups