Many NIPs are simply bad. People just write one without implementing and experimenting first.
Discussion
Also true. I'm guilty of this as well of course
To all developers:
Rushing NIPs is a fiat enterprise way of thinking. It is dangerous.
In a fiat company, for example, managers just propose shit features constantly without doing much minimal viable researches and make developers work like slaves and waste lots of time.
Eventually this model always leads to massive layoffs and both managers and developers pay for it.
If NIPs become the reincarnation of such a stupid enterprise, all of us are doomed.
As NIP1 wisely states, a NIP should be implemented by 2 clients and 1 relay to pass.
We should take it further to say that a NIP should at least have 1 working implementation to even be discussed publicly.
Don’t be the stupid manager who just brings up another idea in the sprint planning.
I noticed some web3 companies use proposing NIP as a way to attract funds
Interesting