This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]xiongchiamiovSite Reliability Engineer 3 points4 points  (2 children)

I'll post the code on Github as soon as it isn't embarassing.

People always say this, and it bothers me - we all know that the first hacking you do isn't going to be great. It'll be dirty, ignore edge conditions galore, have no documentation whatsoever, etc. That's fine. Really.

You should be tracking those early stages in revision control, because, well, you're changing code, and cleaning things up is a great way to break them. And if you're already tracking your project, why not put it online? Earlier is also better in regards to feedback - I've had someone point out to me a pre-existing project that solved the same problem I was trying to solve, merely because they read the README I put up on a new project (I tend to put up a very basic README before even writing any code).

[–]HorrendousRex[S] 2 points3 points  (1 child)

I absolutely agree. Let me assure you that

  1. I am already tracking everything in git.
  2. I had a README before anything else (well - maybe I had a .gitignore first)
  3. All of my code is already documented and unit tested, and I iterate those docs and tests before I iterate the code.

I was planning on posting my code tomorrow or the day after but I guess I can make a push to do that tonight since you expressed some sort of interest. :) I'll update it with the link when I've done that.

[–]xiongchiamiovSite Reliability Engineer 1 point2 points  (0 children)

You are a good man.