Not quite ready for prime-time

I have a lot of
code hanging around, and the techniques in that code would likely
help people who are getting started with .NET, but I haven't had to time to
"polish" it up for public release...

I'm starting to wonder, with the rapid
pace of technology, if I should just release things as they are and tweak later
if I have time... at least they will provide some benefit to some people. If I
wait until I get around to tidying them up, the need for these samples might be
less... hmm... I just hate posting code that I've never polished, it is like
having company over without cleaning up. Thoughts?

Comments (4)

  1. Andy Smith says:

    with, i usually spend in inordinate amount of time cleaning up and preparing code.

    however, with a blog, i think people kind of expect it to be a bit raw.

    here’s the thing… can it really hurt anything?

  2. I know that I (as a learning .NET developer) don’t mind seeing some "rough" code. Sometimes I even find it more usefull than polished code.

  3. Addys says:

    If the code duplicates material which is readily available on GOTDOTNET or other starters sites, then I would pass on releasing it – there is no lack of quality material in that category. But if the code demonstrates techniques which more than just a keyword search away then they are definitely worth releasing, even in a rough form.

  4. John Tobler says:

    A lot of Open Source projects now considered "solid" once started as preliminary code sketches someone decided to contribute. If your code proves useful, people will improve it; if not, it will gradually dissipate into bit dust. If your code might help someone learn, bundle it as a little tutorial. If it is non-trivial, contribute it as a "thought jogger" to kick-start the creativity of the .NET community.

    Certainly, you do not want to soil your reputation by releasing obviously crappy code that people will remember you by; but, we all use code daily that was once little but an interesting and imperfect "first pass."

Skip to main content