It's not easier for me. I propose so much crazy stuff that people just ignore my NIPs these days... "There comes Vitor again". I found that it's easier if I just convince somebody new to send the NIP than sending it myself. Reviews are softer because everybody welcomes a new person. Less biases. In that way, I can also see if people are liking it because of the idea or just because it's coming from Amethyst and will be implemented anyway. I do appreciate the criticism over the idea itself.
Login to reply
Replies (3)
But I consider myself a really good NIP writer. So, that helps me for sure.
We've made one attempt at a NIP. It was a disaster. LOL Haven't decided, if we should make another attempt.
The process is annoying only if your ego is in the way. Once I learned how to avoid that bias, things become just about technicalities: is it the best way of doing it, is it too simple, or is it too hard? Too prescriptive or too broad and vague?
Most of those answers are subjective and thus most decisions on the NIP repo just reflect the "feelings" of devs in the debate.
Once you understand that, you stop caring about perfection and engineering qualities and start caring more about "are people actually going to code this shit and is it actually useful?"...