Yobai wrote on Feb 21^st, 2014 at 11:13am:


Bro, we need to talk about your taste in women.   
Going for aggressive lesbians is always going to end badly for you my testosterone laden friend.
Pretty sure Tolero is not fond of your solo bukkake ideas...

DropBear wrote on Feb 19^th, 2014 at 5:03pm:


I'll answer with my two snow covered Euro-cents :
1) yes.
2) yes.
3) they gets prioritized in term of revenue impact, not in term of game impact.
4) they come back, 'fixed' eventually... the problem is the marketdroids that are all powerfull and set in stone release dates before all the fixes came back and could be validated.
5) not really... it gets filed and prioritized, and then sent to the codemonkey guilty of the piece of code where it is located. Once the monkey has dealt with the bug it should come back to be checked. Now everybody in First or Second line of support or everybody in QA knows that that the codemonkeys know shit when it comes to fixing bugs. But modern job descriptions says First line of support is not allowed to fix bugs ( we can't have the front line soldiers being more competent than monkeys, we just allow them to file the fucking bugs, eventually prioritize it [ and we don't care about hte prioritization anyway ], and make sure all the (ir)relevant KPIs are met ), that Second line of support is not allowed to fix bugs ( they are barely allowed to try to reproduce them and meet the (ir)relevant KPIs ). It's the same for QA, they are not seen as an investment to reduce future loss of revenue, but as just a plain loss of revenue, so they are the first thing that gets scrapped when the schedule goes too tight to fit everything. ( that's for the last line of defense. )

The last line of defense has shifted long ago at the customer end.
The Customer is the tester that finds the bugs. It's way cheaper that way, and lo behold, it's been hitting the Telecom Industry hard in the last 10 years... Expect your phones to works in a less than reliable manner as technology evolves further away from the good old granpa circuit switched phone.

The epic destiny exaulted angel and the stacks it creates when you used a light based spell or heal based spell.

I like the light nuke when you can use that 10 stack because it would heal the group and do damage to the mob boss, made shrouds an even more mindless piece of cake actually.

I stopped playing because of this specific bug.  Just couldn't stand it anymore.  When you let the stack decrease by 2, it will not increase in stacks until the stack is reset to 0.  So if you didn't have anything to kill and you let it drop down from 6 to 4, you had to wait.  Work around was making sure to use the ability that you can at 5(can't remember) so that you could clear it if you knew you didn't have anything to kill real soon.

It also fucked up the transformation counter since you had to get so many of the basic counter(I think, been a while) before it would add 1 to "reborn in the light"(I think but again not sure.)

Did this bug get fixed?

Dark_Helmet wrote on Feb 23^rd, 2014 at 1:15am:


That is disturbing to hear Dark.
Big difference between having to replace your phone handset and having a plane drop out of the sky.

Flav wrote on Feb 23^rd, 2014 at 2:52am:


And this is different from the old system having large banks of batteries in order to keep 48v on your phone lines how?

mystafyi wrote on Feb 23^rd, 2014 at 7:45am:


Well there's no batteries...
In the old ways of doing things there would have been batteries to at least alleviate 99.9% of the power outages.
In the new ways of doing things the operators don't bother with the batteries, they are too expensive to buy and maintain. Just cutting this expense give orgasms to beancounters in Telco.

Flav wrote on Feb 23^rd, 2014 at 2:52am:


I know Flav, I realise you work in telecoms infrastructure.
I was just making a point, albeit inaccurately. 

Even a serious communication or power network outage is likely to be less lethal than a commercial passenger jet having its software reboot mid-flight.

The point each poster is making is that financially driven decision making is becoming all pervasive and is not a good thing.
The decision making is being driven by short-termism.  KPI's and market forces are all short term incentives.
Some industries are particularly bad at manipulating the market and will report anything.
Banking sector is no better, and appears not to have learnt anything from the GFC.   

NOTSunnyshadow wrote on Feb 23^rd, 2014 at 11:43pm:


Well, they hit the bottom lines, so the beancounters are having heartstrokes over the losses the generate. They have to be fixed ASAP, that's an order from the beancounters.
And you can't dodge orders from beancounters nowaday in the industry.

DropBear wrote on Feb 24^th, 2014 at 1:50am:


That's debatable... Trust me I've seen and heard about serious telecom network outages that created enough problem that emergency services ( Gendarmerie, Firemen, ER mobile units ) were dispatched to strategic locations in towns to be reachable at all time by running there. ( because the fucking public exchange that handled the telephone there was down... and did not want to come back up after several hours of poking and prodding. True it won't be all in one single event... but a telecom outage can still be quite lethal if you are in need.

DropBear wrote on Feb 24^th, 2014 at 1:50am:


Yup... KPI driven industry is really bad, especially when the KPI are defined by the beancounters, since the only thing that matter to them is how good is going to look the quarterly report.