Bugs, solutions and documentation: Fast problem solutions can be realized if we have good documentation that helps us to identify where and what to change to get rid of bugs.
Why is it important to properly test everything we create before we release it? Let say that we develop some script for something. It works perfectly in one environment but suddenly it appears to give other result in another one. That is what we call a bug. Some kind of bug at least.
Are bugs dangerous?
They do not have to be dangerous but it is annoying if they give us wrong result. However it is good if nothing goes wrong before we discover the bug. That is, it is especially great if no users experience mistakes.
On the other side if it happens it is very important that developers take care of the problem.
A bug will never be reported by it self so if no one reports it, it does not exist. So it is important to report bugs.
Every bug probably has a logical explanation and in best cases problem solutions can be fast. If a developer can not see / generate a problem while testing something it does not mean that the problem is impossible to solve.
Working with WordPress and developing plugins for it is an area where mistakes can be done. So one good method is to test everything we do in different WordPress sites just to be sure that we get what we expect. Thinking right in plugin development can lead to right satisfaction.
Fast problem solutions can be realized if we have good documentation that helps us to identify where and what to change to get rid of bugs. WordPress as a tool that always gets new updates is a very sensitive area and a good documentation can be our tool for right problem solutions in right time.