Quote:
Originally Posted by
TheVictorious
I think no one can be annoyed from bug more than me, BUT as I'm senior developer and know how things going you really guys need to understand why some bugs solved quickly and another not:
Well, ... I, myself, am not a "senior developer". My job is usually helping software development companies moving from failure to success.
I did develop software for about 2 decades, though. So, I have a different take than you.
Quote:
* First of all, what make it priority or not is what effect of bug not is it give player benefit or not, imagine if they delayed the farm fix issue, and you destroyed your all regular farms (like what a few players did) and then got fixed, you will blame BB again for delaying of fixing bugs?
Some things are quick and easy to resolve with a simple front page post: "WARNING: Improved Farms will be modified with the next update!"
We call this "Minimum viable change".
Quote:
who told you they fix what only give a player benefit?
Who told? It's an impression that customers get. If you want to leave a positive impression, the easiest way to do that is by improving communication and ... admitting mistakes. Not just the mistakes that make players suffer "Oooh, you got more than you should. SLAP." (remember Storehouses, anyone?)
Will players get recompensed for the hundreds of collectibles they are missing? The 75 Pumpkins they lost? A statement of apology for the missing achievement?
The event is OVER - and nothing so far.
Let's get back to the priority issue. You don't need a fix for something that's no longer in use. Not fixing something while it still matters may also be called "Complete failure". They failed to fix it. Simple as that.
Quote:
* Another point, what make a bug most important than another is that bug know for players as a bug or they really think its a normal behavior?, because if you think its just normal behavior you might build your city on that bug, and once its solved, your city all will be down.
Like I said - a frontpage announcement would have clarified that. People who can't read also don't plan strategy based on information text. But even a Dr. Dr. Dr. PhD. MSc can't help with technically impossible constraints. Simple as that.
Quote:
* Fixing bugs is not ABC , and not all bugs are clear in code like its is looks like
BDD, TDD, CI, DoD, Code Conventions, Style Guides, Emergent Design, yada yada. Poor craftsmanship is no excuse for poor service.
Inability to understand modern engineering practices isn't an excuse, either.
But hey, maybe [Removed] will help a bit.
Quote:
some of bugs can be solved quickly like just a change of variables like what was in farm issue the value of levels was still 1 , another bugs related to logic of code that hidden somewhere inside hundreds of code lines
I know that "can be". But: It [Removed]shouldn't be.
Again, poor craftsmanship is no excuse for poor service. Especially not when it's the same guys who have the problem as who wrote the code.
Quote:
it could be a side effect of another feature
That's a common problem if you're not using [Removed]SOLID principles.
But again - poor craftsmanship is no excuse for poor service.
Quote:
so if its changed, that feature might be got broken and things getting worst, so sometimes need to re-write all the code again and again.
Yeah, that kinda stuff happens when you don't [Removed]know how to produce quality software.
But again - poor craftsmanship is no excuse for poor service.
Quote:
* This game come with continuously events, and weekly maintenance what you think developers doing in these days?
What matters is probably more how their Product is being planned. That's not a developer reponsibility. Poor Product Ownership is the root of many problems, but BB is working more PMI-style, so we probably see a whole bunch of managers prioritizing, which - of course - implies that priority decisions can't be made swiftly.
Quote:
* Lastly do you really know anything about developing to say what you are saying ?
At least enough to earn my living. But judge yourself.
Please don't post outside links.