Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

When should I release my code? [closed]

I've been holding off on releasing a library I wrote because it is the first library which I'll be releasing publicly. Here are my concerns:

  1. The library isn't complete it is in a very usable state, I'd say it is version 0.3, however it still lacks a number of features which I would like to at some point implement, and control how they're implemented (meaning not merging someones implementation).
  2. I'm fearful of criticism, I know there are a few things which should be reorganized/refactored, but I wrote the initial class quickly to be functional for another project I am working on.

So when is the best time to release? Should I just throw it up on github and work on the issues post-release? Or should I wait until I refactor and feel completely comfortable with what I have written?

Most classes/libraries I see are always very elegantly written, however I have not seen any in very early release stages, are a lot of classes fairly sloppy upon initial release?

like image 833
tplaner Avatar asked Nov 28 '22 00:11

tplaner


2 Answers

Release early, release often.

Criticism is a good thing as long as its constructive. Ignore the haters, pay attention to the folks filing bug reports and commenting.

The internal structure of the code matters, but it matters more if it works for its intended purpose. In general, refactoring will change how code works internally but will not affect how it is used. Same inputs and outputs.

like image 51
Freiheit Avatar answered Dec 10 '22 13:12

Freiheit


You need to get something half-way useful first, and then others will say "hey, that almost works for me", and they'll get involved in the project.

Linus Torvalds
Linux Times (2004-10-25).

like image 38
Gary Willoughby Avatar answered Dec 10 '22 14:12

Gary Willoughby