ers101284b14_ESO wrote: »If I thought it was the same team doing it I would say yes. But since its not no.
ers101284b14_ESO wrote: »If I thought it was the same team doing it I would say yes. But since its not no.
That's my point - they need to pull the content team and give their energy to fixes.
-
Just temporarily... a couple months at most.
LonePirate wrote: »Apart from another unwanted Veteran dungeon (City of Ash), I don't think we are receiving much new content in update 5, unless they surprise us. You would think that would be a good update to push for fixes but there are no reasons to think so. Update 5 seems like it may top update 2 as the worst update by far.
ZOS_GinaBruno wrote: »There are no new motifs or styles going into Update 4, but we are planning on adding a new style in Update 5.
ers101284b14_ESO wrote: »ers101284b14_ESO wrote: »If I thought it was the same team doing it I would say yes. But since its not no.
That's my point - they need to pull the content team and give their energy to fixes.
-
Just temporarily... a couple months at most.
Thats probably not how it works. what most likely happens is
Team A- Content A
Team B- Content B
Team C- Content C
Team A finishes content
Gives it to main team to push live
Main team finds problems and starts fixing meanwhile Team A starts Content D
Team B Finishes Content B
Gives it to main team to push live
Main Team finds problems and starts fixing meanwhile Team B starts Content E
ect ect ect.
In other words, do you think new content should be put on hold in favor of fixing all "broken" content?

ers101284b14_ESO wrote: »ers101284b14_ESO wrote: »If I thought it was the same team doing it I would say yes. But since its not no.
That's my point - they need to pull the content team and give their energy to fixes.
-
Just temporarily... a couple months at most.
Thats probably not how it works. what most likely happens is
Team A- Content A
Team B- Content B
Team C- Content C
Team A finishes content
Gives it to main team to push live
Main team finds problems and starts fixing meanwhile Team A starts Content D
Team B Finishes Content B
Gives it to main team to push live
Main Team finds problems and starts fixing meanwhile Team B starts Content E
ect ect ect.
The best analogy I can come up with to explain the situation is this;
You have a team of people; a tank (new content), a healer (customer support) and two DPS (bug fixing). If the DPS is taking a long time, the solution isn't for the tank and healer to abandon what they're doing to help out; it's to simply be patient with the DPS.
Best I could do.
The best analogy I can come up with to explain the situation is this;
You have a team of people; a tank (new content), a healer (customer support) and two DPS (bug fixing). If the DPS is taking a long time, the solution isn't for the tank and healer to abandon what they're doing to help out; it's to simply be patient with the DPS.
Best I could do.
Out of curiosity, how often have you toured ZOS? Or how much do you really know about their internal structure? How many years have you been coding professionally, yourself?
It's frustrating when so few can understand what's proposed. Head + sand = bad.
If I walked into ZOS today, I'd really expect more to see a "deployment" team, a "content" team, a "fix" team, a "support tools" team, and a "QA" team. Nothing goes live without full QA, of course. However, when QA finds an issue, it's documented and sent back to the original owner(s) for review & revision.
You have a team of people; a tank (new content), a healer (customer support) and two DPS (bug fixing). If the DPS is taking a long time, the solution isn't for the tank and healer to abandon what they're doing to help out; it's to simply be patient with the DPS.
... [have] the person / people who originally wrote the product dive in to chop down that backlog on a short-term basis is not that hard to do.