ZOS, let me ask you this - What will you do once the console players realize that they've been handed an unfinished game just like on PC? What will you do when Round 2 of the bad reviews come in simply because launch was rushed out the door before the important systems were fully implemented, just like on PC? What will you do when console launch fails to sell those many millions you were hoping for because of the bad reviews, just like on PC? I
Sphinx2318 wrote: »P.S. Please Buff DK's
Sphinx2318 wrote: »P.S. Please Buff DK's
If you stack on crown, you get buffs much easier!
Honestly I think we can all agree that Imperial City was ready more than 6 months ago..Only recently we found out why they are holding everything back..DLCs..Sad but True..
My guess is simple. Imperial City (and maybe even Wrothgar) is more or less ready but if they released it now they would run out of content for at least a year. Because that's how long it takes to develop content like that. That's not even a bad thing, that's simply how long it takes. So what are they doing instead? They are releasing an update with one single purpose only: To stretch the already existing content to eternity. I mean people, seriously... Whether you like the Champion System or not... But it's designed to be a massive timesink, nothing else. The "real" content will be distributed over the course of the year instead.
lordrichter wrote: »My guess is simple. Imperial City (and maybe even Wrothgar) is more or less ready but if they released it now they would run out of content for at least a year. Because that's how long it takes to develop content like that. That's not even a bad thing, that's simply how long it takes. So what are they doing instead? They are releasing an update with one single purpose only: To stretch the already existing content to eternity. I mean people, seriously... Whether you like the Champion System or not... But it's designed to be a massive timesink, nothing else. The "real" content will be distributed over the course of the year instead.
Right idea, wrong reason.
They are largely done with the content, but to release it now would pull resources from the console, particularly in the QA department. It would also add to the QA demand for the console because more content would have to be tested.
@LonePirate , this applies to your last statement, too.
LonePirate wrote: »I have long believed ZOS employs more people to moderate these forums than to perform QA on the game. There may even be more forum moderators than developers.
Regardless of that, a lack of paid internal QA employee is still no reason for ZOS to shaft its PC customers and player base. Once 1.6 is released, ZOS should place Beta versions of both the Imperial City and Orsinium/Wrothgar on the PTS. Let the handful of internal QA staff test the console releases alongside a willing army of console Beta testers. Let the PC players Beta test this new content on the PTS - especially since only subscribers will have access to the PTS on March 17.
The players will test that content from top to bottom and will be able to test it far more extensively than ZOS ever could. Once ZOS resolves the mountain of player issues, let the internal team take a couple of days to look at it and fix any of those issues. ZOS can then remove the Beta moniker from it and prep it for a regular PTS release or even a paid DLC release.
PC players would finally receive new content. ZOS resources wouldn't be more inefficiently used than they currently are. Revenue generating products would hit the market faster which translates to a better bottom line for ZOS. Everybody wins in this scenario. It is insane that ZOS is not doing this.
LonePirate wrote: »I have long believed ZOS employs more people to moderate these forums than to perform QA on the game. There may even be more forum moderators than developers.
Regardless of that, a lack of paid internal QA employee is still no reason for ZOS to shaft its PC customers and player base. Once 1.6 is released, ZOS should place Beta versions of both the Imperial City and Orsinium/Wrothgar on the PTS. Let the handful of internal QA staff test the console releases alongside a willing army of console Beta testers. Let the PC players Beta test this new content on the PTS - especially since only subscribers will have access to the PTS on March 17.
The players will test that content from top to bottom and will be able to test it far more extensively than ZOS ever could. Once ZOS resolves the mountain of player issues, let the internal team take a couple of days to look at it and fix any of those issues. ZOS can then remove the Beta moniker from it and prep it for a regular PTS release or even a paid DLC release.
PC players would finally receive new content. ZOS resources wouldn't be more inefficiently used than they currently are. Revenue generating products would hit the market faster which translates to a better bottom line for ZOS. Everybody wins in this scenario. It is insane that ZOS is not doing this.
Let me point you to the Mythical Man Month to demolish your argument. Especially based on supposition, and no hard facts on workload, capacity, and ability.
LonePirate wrote: »LonePirate wrote: »I have long believed ZOS employs more people to moderate these forums than to perform QA on the game. There may even be more forum moderators than developers.
Regardless of that, a lack of paid internal QA employee is still no reason for ZOS to shaft its PC customers and player base. Once 1.6 is released, ZOS should place Beta versions of both the Imperial City and Orsinium/Wrothgar on the PTS. Let the handful of internal QA staff test the console releases alongside a willing army of console Beta testers. Let the PC players Beta test this new content on the PTS - especially since only subscribers will have access to the PTS on March 17.
The players will test that content from top to bottom and will be able to test it far more extensively than ZOS ever could. Once ZOS resolves the mountain of player issues, let the internal team take a couple of days to look at it and fix any of those issues. ZOS can then remove the Beta moniker from it and prep it for a regular PTS release or even a paid DLC release.
PC players would finally receive new content. ZOS resources wouldn't be more inefficiently used than they currently are. Revenue generating products would hit the market faster which translates to a better bottom line for ZOS. Everybody wins in this scenario. It is insane that ZOS is not doing this.
Let me point you to the Mythical Man Month to demolish your argument. Especially based on supposition, and no hard facts on workload, capacity, and ability.
Brooks' Law doesn't truly apply to my suggestion because I am not advocating more developers. I am not dividing a static development workload among more developers which is the basis of the book you linked. Rather, I am advocating the utilization of knowledgeable manpower on a related task which is gathering dust due to inactivity. ZOS is focused only on 1.6, the cash shop and consoles at present. They have pretty much confirmed this via all of their actions and statements. New content for PC players is not a priority for ZOS at present.
My suggestion effectively alters the project schedule and gives new content to the PC subscribers in about a month instead of 5-6 months down the road. Are you against such a change because of a 40 year old book on software development?
Most of us DC don't care for thornblade but only a few go there for pvp action but our main is chillrend.jjf42001_ESO wrote: »
LonePirate wrote: »LonePirate wrote: »I have long believed ZOS employs more people to moderate these forums than to perform QA on the game. There may even be more forum moderators than developers.
Regardless of that, a lack of paid internal QA employee is still no reason for ZOS to shaft its PC customers and player base. Once 1.6 is released, ZOS should place Beta versions of both the Imperial City and Orsinium/Wrothgar on the PTS. Let the handful of internal QA staff test the console releases alongside a willing army of console Beta testers. Let the PC players Beta test this new content on the PTS - especially since only subscribers will have access to the PTS on March 17.
The players will test that content from top to bottom and will be able to test it far more extensively than ZOS ever could. Once ZOS resolves the mountain of player issues, let the internal team take a couple of days to look at it and fix any of those issues. ZOS can then remove the Beta moniker from it and prep it for a regular PTS release or even a paid DLC release.
PC players would finally receive new content. ZOS resources wouldn't be more inefficiently used than they currently are. Revenue generating products would hit the market faster which translates to a better bottom line for ZOS. Everybody wins in this scenario. It is insane that ZOS is not doing this.
Let me point you to the Mythical Man Month to demolish your argument. Especially based on supposition, and no hard facts on workload, capacity, and ability.
Brooks' Law doesn't truly apply to my suggestion because I am not advocating more developers. I am not dividing a static development workload among more developers which is the basis of the book you linked. Rather, I am advocating the utilization of knowledgeable manpower on a related task which is gathering dust due to inactivity. ZOS is focused only on 1.6, the cash shop and consoles at present. They have pretty much confirmed this via all of their actions and statements. New content for PC players is not a priority for ZOS at present.
My suggestion effectively alters the project schedule and gives new content to the PC subscribers in about a month instead of 5-6 months down the road. Are you against such a change because of a 40 year old book on software development?
That 40 year old book on software development does apply today, and does apply to this instance- which would be one of the reasons that this 40 year old book is still currently in print and in use, when others have fallen out of print and are not even referenced anymore. Your lack of understanding on that point sort of undergirds the original statement. The book and the ideas and practices are based on people, not technology. And people haven't changed that much in 40 years, as shown by the fact that we address the same problems today that we did when the book was written.
I'm... skeptical if any amount of explanation would get that across to you, but I will attempt in any case.
The principle is communicated in terms of developers, but development resources follow the same pattern. Just because we're talking about QA, doesn't exempt them from the fact that there is knowledge used and spin-up and spin-down time in the ramping up of projects. We don't know the project variables and such, nor the depth of knowledge on the team, therefore blindly advocating your statements as a fact is indeed a fallacy. This is not to say that it might not be possible. But the corollary is not true because of that admission.
And to call someone's practices insane when the true picture isn't known? That itself is the height of hubris.
LonePirate wrote: »I understand the concept of the book. In layman's terms, two people don't bake a normal sized cake faster than one person can bake it. My argument - which is supported by everything we can observe and have been told - is that the cake is not being baked. I want someone to start baking that cake while you seem to think someone is already doing that because you are essentially espousing the position that more cooks should not be brought into the kitchen. That's the philosophical difference we have here.
LonePirate wrote: »Also, there is no ramp-up time for the activities I propose apart from creating a build package for the PTS, deploying it and composing a couple of sentences in patch notes or their equivalent. The players on the PTS don't typically need more than that as they are already knowledgeable with the game's mechanics and they would be tackling content that is much more intuitive and simplistic than the skills overhaul and Champion System.
LonePirate wrote: »And if hubris is the term you wish to use to describe a recommendation that increases satisfaction of both customers and the business owners, then I am guilty as charged! From a PC player's perspective, the decision is an easy one when it comes to accessing content in one month or in five months - content that was demoed seven months ago.
LonePirate wrote: »I understand the concept of the book. In layman's terms, two people don't bake a normal sized cake faster than one person can bake it. My argument - which is supported by everything we can observe and have been told - is that the cake is not being baked. I want someone to start baking that cake while you seem to think someone is already doing that because you are essentially espousing the position that more cooks should not be brought into the kitchen. That's the philosophical difference we have here.
The thing that you are missing about the content of the book is that two resoruces- of separate skillsets and knowledge, and are not plug-in freely exchangeable parts. And that's just one thing that an interpretation from a wikipedia article and blurbs on the book will not reveal.
Your analogy of baking a cake again shows a lack of knowledge of the subject matter of the book. Because that's just one aspect, and if that was the only thing covered by the book, then it wouldn't be held in such high regard.
To bring it back to software development and systems and things that *are* known... you wouldn't expect Brian Wheeler to pull in someone on Nick Konkle's team to make up for a lack (whether due to turnover, sickness, or something else), and expect the same level of productivity. The same with all other development resources.LonePirate wrote: »Also, there is no ramp-up time for the activities I propose apart from creating a build package for the PTS, deploying it and composing a couple of sentences in patch notes or their equivalent. The players on the PTS don't typically need more than that as they are already knowledgeable with the game's mechanics and they would be tackling content that is much more intuitive and simplistic than the skills overhaul and Champion System.
This shows such a lack of understanding of the basic concepts required that I realize I shouldn't have even started this conversation. Even the creation of the patch notes is an undertaking- as shown by the time that it takes them to do it every time they release a patch.LonePirate wrote: »And if hubris is the term you wish to use to describe a recommendation that increases satisfaction of both customers and the business owners, then I am guilty as charged! From a PC player's perspective, the decision is an easy one when it comes to accessing content in one month or in five months - content that was demoed seven months ago.
I realize that everyone always wants more... especially when more has been demoed. I can tell you from personal experience, a demo is called a dog and pony show for a reason. We don't know what state things are in behind the scenes, and how close to release ready they are.
We don't have intimate knowledge of what has been done and what can be done is all that I'm saying at its root. And if you can see that certain things being released would help with perceptions and such- do you think that you're the only one that would see such things? And so... there might be other things that you *don't* see? That's the hubris that I'm talking about... the belief that because this is the way that I see things, that it must be true and they must be blind. Even though they have the full picture and I don't.
LonePirate wrote: »I am not sure why you seem intent on bringing up code development at every turn when my original points were related to a lack of QA resources (which are not the same as development resources) and a lack of (access to) content by PC players. Having seen countless bugs in release after release in addition to my own professionally employed experience for several years in software QA, I confidently believe the average PTS tester is as good as the average ZOS tester.
