There's been too many technical questions lately, I'm throwing a few management questions out there:
Is there a limit to how many DACs should be launched in one day? one week? one month?
As an industry, we've got a lot in the pipe and Murphy's Law dictates that all developers could finish on the same day! (Especially since they all get the same 90%-done head start from using the same toolkit.)
As a thought experiment, if we (as an independent community of developers) did have a whole batch ready to go at about the same time, which would be better?
1. Hold them to launch all at the same time to generate a blazing mile-high spike of buzz?
2. Launch them serially, separated by days, weeks, months to give each one chance to be flavor of the day/week/month?
Should their snapshots be done all at the same time or spaced out as well?
What's the best roll-out strategy?
I think 2-4 weeks apart is best. Snapshots should be staggered as well.
Just think...
* LottoShares (TY freetrade for buying us time)
* XT
* ME
* .p2p
* Lotto (BitShares)
* X
* Music
???
* Voting
* MAS
1. I cannot agree more. 2~4 weeks seems to be the perfect strategy.
2. If the problem Stan was talking about would really happen, it basically means that we could see the the dawn of the victory.
3. However, al least until now, things are not so optimistic. no product has been finished yet and the price of PTS reflects the doubt and the fear of the investors. We are losing the market. people even doubt that if there will be really some products coming out or when these products are released, if there will be big bugs which could destroy the whole thing.
4. At last, I just want to say that: Hope the first product---BTS--- could come soon and well.
PS: Can we have a rough date about the release day? I am a little worried that by the end of this year, BTS will still be unfinished.
Don't worry, be happy! Our optimism is higher than ever. Risk is profoundly lower than when we started. Team productivity is skyrocketing.
There is a Darwinian natural selection process going on.
Those who are able to see and correctly assess our status will thrive.
And those are the ones we think should thrive.
Survival of the Fittest!
:)
Well, people should not be surprised if there is at least one such snapshot coinciding with the end of AGS donations ...if not sooner. It just makes too much sense from a savvy marketing promotion point of view.
NOTE: This is not a promise, I am merely issuing the airdrop equivalent of a tornado watch. :)
"A watch is issued when conditions are favorable, for example, either for a severe thunderstorm or tornadoes."
-- Senior Meteorologist Dan Kottlowski, AccuWeather.com
There's been too many technical questions lately, I'm throwing a few management questions out there:
Is there a limit to how many DACs should be launched in one day? one week? one month?
As an industry, we've got a lot in the pipe and Murphy's Law dictates that all developers could finish on the same day! (Especially since they all get the same 90%-done head start from using the same toolkit.)
As a thought experiment, if we (as an independent community of developers) did have a whole batch ready to go at about the same time, which would be better?
1. Hold them to launch all at the same time to generate a blazing mile-high spike of buzz?
2. Launch them serially, separated by days, weeks, months to give each one chance to be flavor of the day/week/month?
Should their snapshots be done all at the same time or spaced out as well?
What's the best roll-out strategy?
IMHO, 1 would be a train wreck, 2 maybe but too arbitrary. Better:
3. Launch each only once acceptance tested by the community and critical staff and procedures are online and prepared to handle the workload on all cylinders.
There's been too many technical questions lately, I'm throwing a few management questions out there:
Is there a limit to how many DACs should be launched in one day? one week? one month?
As an industry, we've got a lot in the pipe and Murphy's Law dictates that all developers could finish on the same day! (Especially since they all get the same 90%-done head start from using the same toolkit.)
As a thought experiment, if we (as an independent community of developers) did have a whole batch ready to go at about the same time, which would be better?
1. Hold them to launch all at the same time to generate a blazing mile-high spike of buzz?
2. Launch them serially, separated by days, weeks, months to give each one chance to be flavor of the day/week/month?
Should their snapshots be done all at the same time or spaced out as well?
What's the best roll-out strategy?
Launch them independently. It's not really important that they launch at once.
Think of it as game titles, as long as you show you can launch that first title then you can use the success of that to launch the rest. It's also good to give people 2 weeks warning so they can generally save their money or prepare.
So I would say give each launch about 2 weeks to itself. If you can launch more than one chain in the same week then do it but it's not something to plan for.