Content
@
0 reply
18 recasts
21 reactions
Zach Harris
@zachharris.eth
Been thinking a lot about what happened with the @precoin fiasco with $w over the last 24 hours. Rereading Boro’s post mortem. Hoping for the best, planning for the worst, this is the way. What appears to have happened seemed like the opposite of that. Some more harsh may call what led to this the result of haphazard architectural choices or irresponsible release management. What I’ve heard from many in the trenches is their response amounted to “oops we did it again”. Protecting users trust and predictably naughty permissionless behavior PLUS stating all the risks upfront, should be a given. It wasn’t. The product marketing language implies earliest alpha ie. Block 1. I’m not salty about a bet that went sideways or loosing money because @farcasteradmin.eth or @jasonkim.eth didn’t test some critical black swan assumptions and rigorous backfill testing. I’m sad the launch went off the rails because of a massive blindspot. Like many, I feel misled.
3 replies
2 recasts
14 reactions
jason (w/acc)
@jasonkim.eth
thank you for the thoughts and also early support gonna patch things and rework things 1000x also see how we can remedy for early precoin supporters and also make sure comms are way more clear going fwd
1 reply
0 recast
1 reaction
Zach Harris
@zachharris.eth
Thanks Jason. I remember hearing somewhere that the path to hell is paved with good intentions. Be careful not to paint a picture of a yellow brick road that just leads to frustration, anger and resentment… You should be operating with a 0% margin of error so early adopters won’t feel this way. So unless $eggs are going to be hatching golden geese, be careful to ape them before they’re hatched.
0 reply
0 recast
0 reaction
