Tips are short solutions to an exception. They are limited in size (256 characters) because we want to present them in a whole as soon as possible when you have problems with an exception. At the moment you will see them
The problem with exceptions during development is that they make you lose focus. Instead of developing what you originally planned now you are trying to understand this unexpected situation, browsing the Internet, reading forums not even related to your problem, etc. The goal of tips is to minimize the time you have to spend with these exceptions and get back to your workflow as soon as possible.
When you have an exception from a third party library, usually it takes 5-30 minutes to understand what happened and how can you fix it, while a tip reduces this time to 1-2 minutes. The reach of a tip depends on the popularity of the library where it helps, but if you write a good tip, it may help hundreds of people every week.
On the other hand, writing tips is a way to improve your profile. Samebug shows the tips you write and the libraries where you solve problems on your profile page, so you can get recognized as an expert of a component.
Currently there are three ways to write a tip:
When you write the tip, you have to write the actual message and optionally you can refer to a url as the source.
You should fill the source url only if tip you wrote is an extract of a content from an other site on the Internet. Please always give credit to the original authors by linking the specific answer:
We know that many information that Samebug deals with might be sensitive, we have an adequate idea about privacy even in this early phase.
In the context of tips written by you these concepts translate to: