Avallo Kantor
Paladin Survey Force
Amarr Empire
182
   |
Posted - 2013.09.22 06:36:00 -
[1] - Quote
M McManus wrote:Delta 749 wrote:M McManus wrote:Iron Wolf Saber wrote:I don't think CCP is betting on this. I don't think you know wtf CCP is betting on, half your post i see, especially here recently; are speculation at best,... Inb4 "But the NDA says I cant talk about this that or the other thing" IWS, Dust CCP and "The NDA" are a laughing stock of this once tight community... Ill take player base under 3k and dropping for 100 Alex!
First of all, you're wrong on the player count. Max player count for today was (at the time of posting according to EVE offline) 4.3k players. There are currently still over 3.1k players online. In what is far past peak hours for NA.
So the player base (even under the faulty assumption that it's the same players that play 24/7) is already well above 3k.
Secondly, what exactly do you expect about him mentioning the NDA? It's an NDA, he can't break it, and that's legally binding. Not to mention for good reason. There was a massive backlash of players when it was announced that tanking changes couldn't make it to the next patch, and players were furious.
Could you imagine how much that frustration would grow if IWS, and other CPM were able to break the NDA, and talk about features that are being planned, only to later hear that they got pushed back? It's well known CCP uses agile development, and what many, many people seem to forget is that Agile development doesn't make code get written faster, it makes a product deliver on time. It delivers on time because by the end of each iteration you deploy a shippable product. No Matter What. If things can't make it, you put them in the backlog. Code doesn't get written faster, features don't finish at a faster rate, the thing that gets faster is the product releasing on time, no matter what has to get cut from the initial run for that to happen.
Generally developers will -try- to make sure that an agile iteration will be 100% doable, but code isn't something you can just bash out, nor does it work like a RL loading bar. Bugs get developed, algorithms sometimes prove to be more complex, and even in the best, most well-written code all sorts of issues can spring up. Classes can have unexpected artifacts, databases can not be updated properly, even the simplest of typos can prove disatrous. (The previous word intentionally misspelled.)
If the NDA didn't exist, IWS could potentially tell you -everything- that was planned for this iteration, all the features that couldn't make it, and the negativity of this forum would increase ten fold. -NO- Developer tells a customer about all the features that were in the beginning of a certain iteration, they tell you what was completed, and what is for future development. (if any) This is not sane, or practical business practice, so of the NDA exists to prevent that. Because of that all IWS can do is "speculate" although, if one were to read what he speculates on and does not, it's easy to see that he is "speculating" with information we do not have access to.
|