Although I would not recommend going through such issues again, I thought it was a good opportunity to discuss some of the positive things to come out of the Jar migration issues.
- Firstly, congrats to the team for how they handled the situation. I am sure it was mega stressful and I doubt they had much sleep, but they kept on communicating and having seen this kind of thing happen elsewhere that led to team/dev silence … this was very well managed.
- The community was awesome too. Yes there were the whiners and moaners and FUD callers, but at a much lower level than I have seen elsewhere. And on the whole the supportive community members didn’t get dragged into name calling or fights.
- Issues that lead to stress and a bit of annoyance, but no loss of funds, will surely bring about improved processes and checking in future. So much of this is new to even the most advanced coders so learning opportunities in a controlled situation are valuable.
- This has flushed out some high profile Pickle fans and collaborations including banteg, who not only has a significant investment in Pickle but mentioned how great the thinking is behind the Jars. I think some people felt like he needed to come to the rescue, but the team already had things 99% under control - not that the assistance of an elite level coder is not appreciated.
- It led to this: https://twitter.com/picklefinance/status/1311831509565878272?s=20 which I am such a huge fan of. The issue now is that the bar is set high so hope this kind of content can continue!
I am sure there are more, but although there are still things being fixed/sorted/migrated/set up I thought it was a good time for positive reflection.