Developer Comments Use Guide

"Developer Comments" is a professional developer software and service review community under SegmentFault. It relies on developers’ real usage evaluation and SF indicators to help developers and companies choose suitable developer software and services, and liberate developer productivity. Facilitate the digital upgrade of enterprises.

The creation of "Developer Comments" is also based on the accumulation of SegmentFault in the past 9 years. Developers who love sharing in the community and an active UGC community atmosphere are the cornerstones of the development of "Developer Comments".

It is reported that "Developer Comments" currently contains hundreds of product information and hundreds of reviews submitted by developers independently. The product categories cover "cloud platform", "development tools", "document knowledge base", and "interface API". , "Development Framework", "Test Tools", "Operation and Maintenance Tools", "Project Collaboration", "Code Warehouse", "Artificial Intelligence", "Data Analysis", "Website Service", "Network Security", "Database" , "Operating System", etc., involving software development, testing, operation and maintenance, AI and other aspects.

Let's take a look at how to use it together~

Didn't find the software you want to review?

First confirm whether your product is suitable for submission here. We are a developer-oriented community. The products here are products suitable for developers, based on helping developers "choose the right tools and services, and liberate productivity." In order to ensure the purity of the SegmentFault comment section, it is recommended to submit the technical service products and tools used by the developers in the enterprise and the technical service products and tools used by the developers on a daily basis.

Before submitting, I hope you have prepared the following documents:

• Product icon: supports jpg/jpeg/png three formats, the size should not exceed 2M, the recommended resolution is 256*256;
• Product introduction: I hope you have prepared a product introduction in advance, a good product introduction can help developers quickly get the essence of the product;
• Product screenshots: support jpg/jpeg/png three formats, the size should not exceed 2M, the recommended resolution is 256*256, and no more than 4 photos.

Prepare the above information and enter the link: https://segmentfault.com/dianping, slide down to the green "Apply to add" on the left, fill in step by step according to the prompts, after the submission is successful, after the background review is passed, you can go online~

Come and make a crazy call for your favorite products

Start review

step1: Enter the product review interface https://segmentfault.com/dianping

step2: find the product you want to review

step3: Start to comment (eligibility for review: registration for more than 30 days and reputation value of 100 or more, if you register for 30 days, reputation value is less than 100, this link to get more tips for improving reputation: 160dd92a5a8227 https://segmentfault. com/repu)

step4: Submit a review (if you don't want others to get your review information, you can choose to be anonymous)

How to write a good review

1. In-depth understanding of the product you are reviewing

Regardless of writing aside, a review that can arouse everyone's "worth a try" or "try to close the hole" of a product, the most important thing behind it is: you have a deep understanding of the product and have used it for a period of time , Can clarify the characteristics of the product sharply.

2. Make a bold comment

Faced with a product, I wanted to comment or suggest improvements, but I was worried that I would encounter the nonsensical criticism of "you do it." Pass on the negative emotions about this matter to others; the second is not wanting to bear the responsibilities corresponding to one's own role. So when you encounter this kind of situation, just ignore it and comment boldly.

3. Your comments are valuable to others

"Developer Comments" hopes to seek information about products or services from many developers through a real evaluation and feedback system, to help developers choose suitable tools and services, thereby liberating productivity. Therefore, when reviewing, I hope that the reviews are authentic and have a clear point of view and attitude, such as the product Amway that improves productivity, or closed pits, mine-stepping guides, etc.

Hope to avoid the following problems

1. Full text software translation/pictures

If you learn from relevant English reviews, you must avoid translating the whole text. This is just to carry other people’s ideas about the product, and only translate each interface of the product with some simple thoughts (for example: "This function is really useful!"), It has no substantive effect on the developers who see this comment in the future.

In addition, just the interface of the product, screenshots and Chinese operation guide, not a valuable comment~

2. Simply apply the "standard" template

In fact, the developer comment platform provides a set of templates, such as: "Which features do you like the most, and where are they good?", "Which features do you dislike, and what are the shortcomings or shortcomings?" analysis. Turning back to the next article found that the same article structure is still used, and yes, turning forward is the same. Regarding this, it’s not to say that applying standard templates is necessarily bad: it does lower the threshold of reviews and can help developers sort out the ideas and structure of reviews, but unchanging reviews can easily be buried in the ocean. Therefore, when reviewing a product, you can try not to follow the old routine as much as possible.

If this is a video playback tool, please tell us why you like it most among the massive spare tires. If it’s a game, we don’t mind looking at the developer’s story, or what innovations are made in the game’s operation, etc.

3. Write a product "instruction manual"

The more words written in the review, the better the quality of the review? In fact, what we want to write is a product review rather than an operation guide. We exhaust all possible aspects of the product, regardless of level and logic, and leave it to everyone who sees it. Such a review is not only useless, but even It's a waste of time, writing reviews as product manuals is simply a disaster.

for example

Dianping among programmers, give an example of Dianping:

Real evaluation + high-quality picture, is a high-quality review, listed above: three suggestions and three no suggestions, in fact, it is just a reference suggestion~

reviews are not difficult, everyone’s reviews are gathered together to give a true evaluation of the product