Participate into an open source project

Don't worry too much about if your project will interest readers. The most likely thing to happen is nobody will even notice or care about what you post. But that doesn't mean you shouldn't go ahead and do it. Somebody might benefit from it.

The second most likely thing to happen is, as SAKryukov points out, people will point out all the mistakes in your code. But at least that means somebody noticed.

Be willing to have your work criticized. Don't get emotionally attached to your code. No matter how good you are, there is somebody out there who can point out a way to do it better -- and there will always be those who think they can. Some of the criticism will be opinion, some of it will be valid -- if you look at it as a learning opportunity, then you'll definitely learn things.

Go for it.

You have some good points I appreciate, especially the point about the criticism. At the same time, I think it's important not to contaminate the community with weak work. A person writing the article should be very strong in the field she or he is writing about. We are not interested in inflation and denomination in publication.

Anyway, open-source development is a great thing by itself and a great tool to earn experience and reputation for the beginners. It does not mean that the quality of open-source products should be compromised. For a good perspective beginner, its the best to work in a team which is capable to accept novice's work and help such developer to maintain required quality of code.
--SA

True. A novice will learn the most by working with an existing project and learning from more experienced team members -- probably a lot more than he will if he posts a project that nobody is interested in.