brillout/rules
Welcome! We 💛 conversations.
In order to keep discussions constructive 💪, we ask you to carefully read following rules 🛡, thanks!
We have a problem with tool X, can you help?Ask tool X instead of asking us.
Our app doesn't work and we don't know why, can you help?Ask us only if you have evidence that your problem is related to our tools.
Your tool currently behaves like this, but it's problematic because...Your problem is clearly related to our tool ✅.
The golden rule here is to try, research, try, research, and try & research again(!) before asking for help.
If you are not well-versed with our tools then you'll most likely find a solution by reading more documentation and trying longer.
If you are a junior developer, you should spend at least something like a couple of hours on one specific problem before asking for help.
If you are a senior developer, you can reduce that time to something like one hour.
If you are well-versed with our tools, you can reduce that time to something like 10 minutes.
That said, criticism is more than welcome: our tools should be ergonomic. Let us know if you believe that a particular aspect of our tool is not user friendly and we'll fix it.
We have this problem. We tried this, that, and that other thing, but without success. Can you help?We can tell you first tried to solve your problem on your own before asking us — you did your homework 👌. We are happy to help.
We have this error coming from your tool.Give us the error's message & stack trace — we'll start fixing the bug right away.
We believe this aspect of your tool is not ergonomic.We are happy to discuss DX improvements.
This part of the documentation is lacking / difficult to understand.Thanks for the feedback — we'll improve the docs.
Can we use your tools to achieve what we want?We are happy to discuss use cases and whether our tools support them.