Killerstorm had some valid concerns around it. Unfortunately, this project seems to lack the technical leadership at this time to have adequately responded to his questions and factored his concerns into the development process. He probably got a bit miffed and then took it publicly.

There is development process control that is sorely lacking on this project currently (and I say that as a dev with 18+ years professional experience that has been working with the existing mastercoin code as I structure a new tool around it). I have several ideas how this can be improved, and would be happy to speak with David or Ron, or anyone else on the board about it if they are interested.

Basically, in the end it's reason #5,490 for hiring a full-time team. On the operational side, this comes down to effective delegation...hiring decisions are the absolute most important decisions one can make. How Ron is running around clearly overwhelmed reminds me of how I used to be before I learned how to effectively hire, delegate, and train new employees. Now my business largely runs itself. Not a critique of Ron himself, and I cannot assume I know exactly what is going on on his end...more just saying that the board needs more dedicated folks with previous operational-level business leadership to help Ron scale out, which I see as Mastercoin's main problem right now. The fact that he just ran off and found someone additional for the board and mentioned it in passing on this thread really irks me. And, if there are people on the board that are "too busy", why are they on the board to begin with?

Anyhow, we need someone like killerstorm leading the charge on the core protocol implementation, to ensure stable growth and backwards compatibility as required. With the budget of this project, why is this so hard to do? If it is really that hard to find people to work for MSC, then offer fiat or BTC at first. At this point, we just need the right talent. It's good to see David in there attempting to diffuse the situation, but we're playing reactive damage control here.