@Fatman3002 : The great thing is it's not really a shitstorm, but just a network upgrade.
As a Bitcoin holder, it's possible to mostly ignore this storm (if you're able to remain undistracted by the price turbulence which is to be expected for this, because some people are making a big controversy out of it).
Anyone who wants to keep playing can just ensure their software handles slightly bigger blocks (2MB would be a good start - 4 or 8MB would be plenty for a while). That's just a couple of places in most code that need changing.
For full EC algorithm, obviously a bit more adaptation is needed by full-node clients (I think we'll put out a better specification / description of the EB/AD algorithm used by BU - but others are free to implement whatever adaptations of it they deem suitable for their clients). e.g. Classic does it slightly differently (no AD as far as I can tell).
The main point is just to make your software configurable w.r.t. block size.
Bonus marks if you implement logic that keeps you on following a chain even if it increases past your configured block size limit.
Gavin has expressed support for the emergent consensus driven upgrade (check his Twitter).