It is normal when a new project that is not fully coordinated properly ends up making the system not run smoothly and lots of problems occur. This already shows that this project is very risky, and there is a possibility that something worse will happen and will make many investors lose money. So be careful when you still have Solana in your wallet.
It's normal when you are building an AAA+ game with a billion moving parts that there will be bugs. But when you are building project that's handling actual finances for people, that's worth ~10-70 billion dollar in the marketcap, then having zero exploitable bugs is quite essential feature.
And Solana dev team STILL has no idea what caused this latest network outage which i find troublesome to say at least.
I don't think Solana's development process is uncoordinated or not fully coordinated, as far as I know there is only one Solana node variant, and it managed by Solana Labs, Inc(
https://github.com/solana-labs/solana).
Also, take a look at,
https://github.com/solana-labs/solana/blob/master/CONTRIBUTING.md. The contributing or development information are pretty clear for anyone, they have their own convention, they have its own development process, code review, etc. Solana pretty much has a highly centred development process, so it is coordinated, also, noting how this issue gets resolved. The nature that node operators are few, makes it easy to be coordinated.
The problem is, how could such mistakes that even the root causes are still unknown be able to get merged on the codebase? What is outrageous is it's not the first time. There must be something wrong with the development capabilities and due process.
