I don’t mind that innovation is impossible to predict. I think what people want is to have some insight in to what the team think at any given moment in time. We know this will change as development progresses. We understand that it is quite likely that some things that are supposed to take weeks end up taking taking months. I don’t think most people expect to have timescales that are accurate, but we want to know what they know. If they currently think a certain job will only take a couple of weeks then it would be cool to know that, even though we might all be as disappointed as each other when it turns out to take a few months.
However, experience has taught the Maidsafe boys some hard lessons. I can see why they don’t want to put themselves in that position. It creates more problems than it solves from their perspective. What we need is SAFE working in the wild, not a team potentially distracted by the inevitable consequences of giving timescales and then missing them by big margins. It chips away at their credibility when they’re wrong and there’s very little ‘win’ in it for them to be right.
I want more info and I want to know what’s going on in the heads of all the team members, but if I was in their position and I’d been through what they’ve been through I’d be staying shrewd and silent in the name of the bottom line - bringing SAFEnet into existence.
Their best play is the same as it has been for a long time now imo; avoid the distractions and risks so they can get on with building SAFE and saving the digital world.
David obviously sympathises with our position, he made a real effort to give some broad dates (a decision that could bite him in the arse in 12 weeks when it’s quoted back to him lol ;)). I think he’s been as revealing as he can in letting us know his broad expectations for the near future (thanks again for that David), that’s as much as we could realistically ask given the circumstances here. He carries a lot of weight on his shoulders and he didn’t need to saddle himself with the additional expectations by suggesting we’d be iterating fast through the Alphas in the second half of this year. As a poker player I see a man making a bad play because of emotion (sense of responsibility/guilt and sympathy). David’s humanity is one of the reasons I have faith in him though. I know he’s trying to do what’s best and to make a difference. Really, the bottom line is getting SAFE out there, not knowing in advance when it will happen. I could imagine regular updates on date expectations could hinder that goal if not handled very delicately. Constant missed deadlines looks bad to the uninitiated in software development and innovation. Having to defend themselves and getting into protracted explanations about the roadmap dates is just more distraction from the only thing that matters.
Meh, I want to know their real-time expectations as badly as the next person, but I agree with David’s policy to be cautious and avoid exposure to unnecessary issues and risks. Same with NVO and any other non-essential, peripheral stuff. if it isn’t going to get SAFEnet launched any faster and it might swallow a lot of time or create issues then steer clear and keep eyes on the prize imo.