I am the author of Beetl and BeetlSQL open source. These two types of technologies are difficult to implement. The former belongs to the language implementation type open source, and the latter is a full-featured ORM implementation. However, these two open source use thresholds are low, and they can meet all kinds of novice users. I helped Xiaobai solve a lot of technical problems, but I also encountered problems caused by Xiaobai. I have summed up the intentional or unintentional harm caused by 9 kinds of Xiaobai to open source authors, and divided them into 3 levels according to the severity
1st level damage, normal damage
chat questions
Xiaobai, who behaves in this way, has never realized that questioning is a discipline, has not studied how to ask questions, and has not observed how other people's questions can be answered carefully by experts. He always felt that the experts were by his side and that the experts had enough time to help him. He usually asks questions like
小白>你好，在吗？
小白>（10分钟后）大神，有空吗？我有一个问题想问问
This kind of novice doesn't know that open source authors are very busy. If he happens to see your question in his spare time, but you don't have a scientific question, he will hardly interact with you on the next thing you want. This kind of pointless harassment of open source authors is quite annoying.
Never read official documentation
This kind of behavior is the most common Xiaobai, and Baidu is used as a tool to solve problems. Xiaobai needs to know a few things about what search engines can't do
- Inquiries about new technologies, small and micro technologies lag
- For popular technology, some people will fall into the sea of information
People who rely on search engines to solve problems will have weak technical accumulation. A better way is to focus on the official website manual, combined with official website forums, or specialized technical communities such as oschina, combined with source code and search engines to find solutions. For Xiaobai, most questions can be answered from the official website documentation. But Xiaobai didn't have time to study the official website documentation. In my experience, the more powerful people are, the more they pay attention to the official website documentation, and the more time they spend reading the official website manual and other technical information on the official website. The more novice you are, because you are busy and do not understand the official website documents in detail, and the knowledge is not solid, which will lead to more and more busy later (because you will always solve the problem that is not the problem), and you will fall into a disgusting cycle.
In my SpringBoot-Plus open source, the installation instructions have 14 lines, 5 lines and the standard focus. They all mention JDK8 and open Parameter parameters, and explain in detail that if an error is reported when the system starts, it should be that the paramter parameter is not available. Open it (I also linked the article on how to open the JDK8 paramter parameter), but there are still more than 10 little whites who told me that the system could not get up, and attached the same error I mentioned in the installation instructions.
These idiots are always asking obvious questions, causing confusion for open source authors and other novice users
Want this or that, without thinking and exploring
This kind of novice has caused the most regular damage to open source authors. Sometimes I suspect that they are not incapable, but lazy, thinking that open source authors are teachers around him, or colleagues around him, for example, they often raise some problems that they can obviously solve by themselves, such as
小白>BeetlSQL如何翻页（实际上官网文档有专门一章讲翻页）
小白>Beetl的Maven坐标是什么（同样官网文档肯定有哇）
小白>SpringBoot-Plus 数据库安装脚本有吗（如果没有，还能叫开源吗，就在doc目录下）
If you really have time to answer this kind of Xiaobai's question, it is not easy to answer. This kind of Xiaobai's question usually requires a large amount of space to answer its questions, because the question is too basic.
secondary damage, normal damage
Emotional catharsis type Xiaobai
This kind of Xiaobai has certain technical ability, but he cannot solve the problem by himself, so he pays too much attention to his own emotional experience in the process of communicating with open source authors, such as
小白>这个问题我花了周末俩天都没解决，难道Beetl真的很不好用吗？（作为开源作者的我，真想一棍子敲打上去，你是不是来解决问题的？）
For example, Xiaobai often works hard until 11 o'clock in the evening, and then asks questions in the QQ group
小白>大家好，问个问题,很着急解决......
小白>(半小时后)，这个群太冷漠了，都没人愿意帮助我
In fact, everyone is reluctant to help. It may be because they are all asleep, or they have no energy to help you solve the problem late at night, but you vent your personal feelings, and it is estimated that you will not get any help from the community the next day.
Selective presentation of problem clues
This kind of novice is the most troublesome for open source authors, because when they ask for help, they don't know what kind of information they need to provide to open source authors. Sometimes even deliberately only show the correct part of their own writing to gain the approval of the open source author. but this doesn't solve the problem
The most common is to just post your own code, but not the error message. In fact, error prompts are more helpful for open source authors to solve problems, even without posting your code. Some people have posted error messages, such as exception stacks, but they have not fully posted the exception stacks. Some people have posted codes, but they have not pasted IDE code lines with the diagrams, which makes communication impossible.
For example, in this map, it is difficult to provide open source authors with detailed clues. The real clues should be in the exception stack that is not posted below.
This map does not contain the number of lines of code, which will cause communication difficulties
A better way is this picture
This kind of novice will waste the time of open source authors, so I think it is secondary damage.
I often say a word, if you ask carefully, I will answer in detail. Usually, I am very welcome to the novice with multiple pictures attached to the community question.
Ask the wrong questions to open source authors
After thinking and exploring, some Xiaobai asked the wrong question. for example
小白>为什么XXX开源不兼容Java7(实际上根本不是版本的事情）
小白>为什么BeetlSQL不支持SQLServer(实际上是数据库配置不正确)
. Such questions can mislead the answerer. The correct posture should be a complete statement of your expectations and your own process and the final phenomenon. Then you can put forward your own solution direction to assist the open source author to help you solve the problem
Hide your background information
There are many ideas for open source authors to answer, and background information is very helpful for open source authors to answer questions. For example, if you are a novice, then SpringBoot-Plus has not been started. It may be that you have not installed Maven or JDK. If you are an experienced SpringBoot person and have used SpringBoot in several projects, then the startup failure may really mean that there is a problem with the environment. Compatible, even open source bugs
When Xiaobai asks a question, it is very necessary to introduce himself in a few sentences, such as
大有前途的小白>我是SpringBoot-Plus使用新手，我有3年java经验，也使用过Spring，自己也实现过AOP，现在有一个SpringBoot的自定义AOP如何实现的问题....
This kind of question is much better than Xiaobai asking how to implement AOP as soon as he comes up. The former can help open source authors know the scope of the answer and answer them accurately, saving the time of the open source author and Xiaobai.
Level 3 damage, heartbreaking
Attack open source authors for poor hospitality and spread rumors
Open source authors are interested in completing open source in their spare time, and they also take time to help answer questions. Therefore, if open source authors do not answer questions, or answer them concisely, this is the normal behavior of open source authors. But some Xiaobai thought they were offended and turned to attack open source authors.
I have suffered similar attacks from two people. They thought I neglected them or embarrassed them, so they turned to attack me in the community. He posted a post on oschina saying "Why is the author of beetl Xian Dafu so arrogant and defiant", and took screenshots as proof. This post has been on the front page of oschina for a month because of its popularity
Some people collect all kinds of black evidence of me in the community because of my neglect. For example, once I saw the memory model in concurrency, I asked a question in the community (in fact, I already knew it at the time), the intention was to let everyone discuss the technology , and as a result, someone immediately sent this screenshot to the community, and then said "Xian Da Fu doesn't even understand concurrency"
Level 3++ damage
Attack the website, hack the open source community of open source authors
This may be Terry, but I came across this little white who is a technician of a large Internet company. He is invincible in the community, and even started to educate others about the morals. As a young man, it was very rampant. After I expelled him from the community, what I didn't expect was that the website could not be accessed immediately, and he had been subjected to brute force cracking, and he also broadcast the destruction process in the community through a small account. The next day, ibeetl.com was really inaccessible, the entire community was hacked, the data was emptied, and the technical Q&A accumulated for 3 years no longer existed.
Later, other people in the community helped write it, rewrote a java forum with SpringBoot+Beetl+BeetlSQL, and even open sourced the project, a blessing in disguise. Far from the wicked, made real friends
Summarize
As an open source author, it is rare and valuable to provide your own ideas and works. If there is a good Xiaobai, then the open source products will be more perfect. If you encounter the various Xiaobai I listed above, it is the misfortune of the open source author. I think this has always been the norm. When you meet a few outstanding Xiaobai, you will encounter a few who will cause various levels to the open source author. Hurt white. I hope that after reading this blog, Xiaobai can reduce the trouble and harm they cause to open source authors, and at the same time improve their technical level