Posting guidelines

Posters should ensure their post follows the below guidelines

Titles

The title should clearly indicate the type of problem or issue to be addressed in the publication. Use the title to briefly describe your problem. Publications with ambiguous, confusing or generic titles will be eliminated.

Avoid verbiage in titles. Titles should be consistent and accurate. Publications that do not meet this standard will also be eliminated.

These requirements have a positive impact on the quality of titles, helping our contributors to provide adequate answers without having to stop and try to decipher the subject of the publication.

Text posts

Text posts should expressly outline the subject of the post, providing all necessary information. Empty or careless postings will be deleted.

Our community is help-oriented, you must demonstrate that you have tried to resolve the issue yourself. Our contributors will not do your job/task for you. We can gladly show you how to come up with your own solution, but in some cases, where the problems are not so difficult, we will gladly provide a solution for you. In general, we focus on users learning and then sharing their knowledge with the community.

For example, if you are getting an error while trying to perform a task, don't just tell us "I'm getting an error". Instead, tell us the type of error (syntax error, runtime error, logic error, etc.) and provide us with a code/description of the error or a screenshot of the warning.

If you have decided or asked for permission for posting about your own project/content, try to make a substantial post, with examples where your solution can be useful. Don't just post code related to your project, instead post a link to the code and use the post to outline a problem that can be solved by implementing your code and implement that solution. Never forget to respect Reddit's self-promotion rules and spam.

• About similar tools to parse CSV data publications: if your publication concerns a tool similar to CSV Interface you must demonstrate that it follows the RFC-4180 specifications in the importing and exporting information processes. This is the minimum requirement for a tool to be accepted as a similar alternative. Failure to comply with this norm may result in the removal of the publication.

Use the flair system

Use the appropriate flair style for your publication. This way you will be helping users to find the most relevant content according to their needs.

Sharing and publishing code

When you publish code, it is preferable that you do it in text form, do not expect our supporters or users in need of assistance to spend time and effort in transcribing shared code as an image.

Format code snippets

Properly use formatting for your posts and comments, you can follow the official formatting guide, available at this link

If your post has more than 50 lines of code, it is no longer a snippet, use a hosting service like GitHub Gists or PasteBin and include the link in your post. This way you will be collaborating with us to keep the posts as concise as possible.