![]() |
|
|
|
#1
|
|||
|
Having been a SW engineer for over 30 years, I can tell you there are two major syndromes when it comes to a new release:
1) Releasing too early, rationalizing major bug into minor problems. Crossing our fingers and hoping that the users don't find that use case you know about (they always find it in 5 minutes while it took your testers and dev team 4 months to run into it). The need for revenue outweighs the anger of the end users. 2) Waiting for perfection. Each bug that has a workaround is rated as a major issue. Aesthetic issues are sweated over because the developer has been staring at the same glitch for weeks but in reality users will never see it because it's usually on screen for 5 seconds. The desire to please everyone outweighs everything else. Both are bad. Problem number 1 results in angry users and a bad reputation. But it can be overcome if patches are forthcoming and actually solve problems. Devs are usually motivated to solve the problems once the pressure of release is behind them. Problem number 2 results in demoralized developers who, faced with the impossible task of creating perfection, simply walk away to find a new project. People need goals that are attainable, even if they at first seem impossible. And they need the rewards of their efforts. People actually using their software is that reward. | ||
|
|
|||
|
#2
|
|||
|
Please delay green because "WHAT IF?!?!?!?"
| ||
|
|
|||
|
#3
|
||||
|
Quote:
The Green team set a goal, release on Oct 25th. Release and move on. If they put it off, they will please N users and anger M users, all while demoralizing themselves. Demoralized devs are definitely not a good thing. So, the question is, is N<M or is N>M? I have a sneaking suspicion that N is much smaller than M. | |||
|
|
||||
|
#4
|
||||
|
Quote:
| |||
|
|
||||
|
#5
|
||||
|
Quote:
If the bugs that people are running into exist on Blue, then it's not a Green issue but something that can be worked on after Green in released. Green seems to be about the timeline, the lighting, and the UI. They seem to have the timeline issues resolved. The lighting looks great, but if there are bugs there, they need to be fixed or people will be hating for good reason. The UI, well, it is what it is at time of release. It won't be pure classic because it CAN'T be pure classic. As long as you can interact with the UI withing hanging, crashing, or dying, its good to go. | |||
|
|
||||
|
#6
|
||||
|
Quote:
| |||
|
|
||||
|
#7
|
||||
|
Quote:
| |||
|
|
||||
|
#8
|
||||
|
Quote:
The worst bug/exploits aren't going to be reported by 90% of the players because they will want to abuse them on release. We have to wait for the 10% to find them. Worse, the class ratios are completely out of whack. Like a buttload of mages/kiters/pet classes. Who knows what kind of bugs could await SK/paladins/rangers 40+. Now you give me a list of reasons you can't wait a little longer for something 10 years already in the making? Why should your demand to PLAY NOW DAMN IT, trump someone else who wants bugs as squashed as possible and as classic as possible? What makes you so special? | |||
|
|
||||
|
#9
|
||||
|
Quote:
https://www.youtube.com/watch?v=BkHjFzw1TUg | |||
|
|
||||
|
#10
|
|||
|
Oh man. Let it go.
| ||
|
|
|||
![]() |
|
|