lips VS problem-diagnosis-remedy-proposal

-- Github

➡️ You can find more information about #LIP0060 at GitHub: https://github.com/LiskHQ/lips/blob/main/proposals/lip-0060.md

GitHub link here 💙

One of the most famous success stories is the Lisk protocol. A cryptocurrency blockchain written in JavaScript using SocketCluster as its peer-to-peer protocol. At the time of writing Lisk is ranked #99 globally according to Coin Market Cap. Here are [1][2] articles related to SocketCluster on LiskHQ's GitHub.

LIP0018

The trick is always convincing people that there is a better way. Because you have such a small team responsible for so much, you really need to establish consensus with some discussion and counter-railroading. I push the problem, diagnosis, remedy proposal model on a lot of my organizations whenever I see that there's not consensus or that there's not much interest in consensus or shared knowledge. Sometimes a "do what you think is right" carte blanche from the team is a good thing when you want to go fast, but when you want to go far together, having written artifacts of your intentions and the reasoning behind them is incredibly important. On a small team, you do not have the luxury of isolation or compartmentalization.