Open source and in-house development?

Question

open source

So the question arose, we use different libraries, which we ourselves wrote.
It is clear that the shoemaker is usually without boots, and they contain many joints that are tolerable within our closed ecosystem, but they could be removed.
On the one hand, it seems that it is possible to finish it, but on the other hand, “it works - don’t touch it”, “it satisfies us” and just laziness.
We do not feel sorry for giving out some pieces of code to the public and for free use, but it's a shame :)
Actually, who thinks about it? Bring to mind? Write detailed documentation? Or xyz with all that?

Answer 1

It seems to me that there is such a delusion that laying out a project in open access will attract active attention to it, including unwanted criticism. In psychology, there is even a term for this: spotlight effect .
At least my experience suggests otherwise: by default, no one cares. Especially if you are posting not a finished product, but auxiliary utilities and your own developments, the use of which requires a certain level of training or involvement. Take a look at our github account for an example . Good, as it seems to me, auxiliary utilities, posted in the public domain, attracted the attention of ... almost exclusively our own employees. So my advice would be:
- Fix frank jambs, if any.
- Make a small README file describing the features and the correct installation method
- Put it on github. Publication on github does not impose serious moral obligations :)
- If you are ashamed to inform everyone about the project, tell only your friends. Suddenly they need it and like it.
Obviously, it doesn't make sense to add functionality that you won't use, and it probably doesn't make sense to add handling for all possible cases if they don't occur in your work. If a project is of interest to the public, you will know about it and act accordingly.
From quickly noticeable positive moments. Making the project publicly available will most likely lead to a higher level of awareness when adding new functionality to the project, which will have a beneficial effect on the overall quality of the code. Still, the idea that someone can do a code review, even potentially, it disciplines.

Answer 2

Don't be ashamed, open source has a VERY VERY lot of bad code, bugs, bugs, etc. etc., even in popular projects.
Well, just do it, it depends on the subject ... if someone needs libraries, lay them out.

Answer 3

unconnected , it seems to me that everything has been described in detail to you. Moreover, your question already has an answer. On the one hand, I want to put it in free access, on the other, I feel ashamed. It is necessary to soberly assess whether an outside interest in your developments is possible. If it is possible (and you want to post it), then you just need to fix those places for which you are ashamed. If you realize that your achievements will not be useful to others, then, probably, you should not increase entropy.
Although there are other reasons for publishing code, for example, PR.

Answer 4

Post it, don't be afraid. Try to at least just put your work in order a little, so that an uninitiated person can use them without breaking their head much. For example, I posted one project on github, having previously made a deb package for it for those who do not want to bother, but just want to use the program. I don't know how to write the makefile correctly, I built the deb in a simple way, but it works. And I think it's better than nothing.

Answer 5

There is such a term "as is". Spread, but catch feedback from users. You will also benefit.