Reply to thread

Message

<blockquote data-quote="wedgeski" data-source="post: 5381096" data-attributes="member: 16212">All it tells me is that there are exigencies which the software developers and project managers of DDI have absolutely no control over, whatsoever, and which override any priorities they hold dear as to the state of the software they want to release.Once upon a time in a planning meeting, someone somewhere decided the CB2 would launch with Essentials. Confidence was expressed by the DDI project manager at the time that such a deadline could be met... so much confidence, in fact, that no contingency was put in place for Essentials and/or Dark Sun support in the existing CB. Or perhaps it was simply a cost issue, we'll never know.Now what has happened is that, for whatever reason, CB2 isn't ready for prime time (and for god's sake, buggy as it is, it's not the train-wreck this board would have you believe), but the schedule had to win. DDI support for Essentials was absolutely dependent on CB2, so it had to be released. Perhaps there was statistical evidence that people were actually changing their spending habits because DDI was lagging (and I mean proper evidence, not the deluge of threats to quit posted on boards like this), or perhaps some manager somewhere had staked his job on it.We can argue forever about what went wrong (planning? feature creep? poor development methodologies? poor testing? simple bad luck because 10% of developer time was lost due to the 'flu?) but we'll probably never know the truth. Landing at a point where you're sure that the software team is inept is understandable, but unfair.</blockquote>

[QUOTE="wedgeski, post: 5381096, member: 16212"] All it tells me is that there are exigencies which the software developers and project managers of DDI have absolutely no control over, whatsoever, and which override any priorities they hold dear as to the state of the software they want to release. Once upon a time in a planning meeting, someone somewhere decided the CB2 would launch with Essentials. Confidence was expressed by the DDI project manager at the time that such a deadline could be met... so much confidence, in fact, that no contingency was put in place for Essentials and/or Dark Sun support in the existing CB. Or perhaps it was simply a cost issue, we'll never know. Now what has happened is that, for whatever reason, CB2 isn't ready for prime time (and for god's sake, buggy as it is, it's not the train-wreck this board would have you believe), but the schedule had to win. DDI support for Essentials was absolutely dependent on CB2, so it had to be released. Perhaps there was statistical evidence that people were actually changing their spending habits because DDI was lagging (and I mean proper evidence, not the deluge of threats to quit posted on boards like this), or perhaps some manager somewhere had staked his job on it. We can argue forever about what went wrong (planning? feature creep? poor development methodologies? poor testing? simple bad luck because 10% of developer time was lost due to the 'flu?) but we'll probably never know the truth. Landing at a point where you're sure that the software team is inept is understandable, but unfair. [/QUOTE]

Verification