|
|
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Cenex Langly
D.A.R.K L.E.G.I.O.N
D.E.F.I.A.N.C.E
691
   |
Posted - 2014.03.25 14:26:00 -
[1] - Quote
Hecarim Van Hohen wrote:Well hopefully I learn to not spend my SP until everything has been fixed and double checked
I'm looking at you Amarr scout skill multiplier
You need to learn that from day 1.
Newb
|
Cenex Langly
D.A.R.K L.E.G.I.O.N
D.E.F.I.A.N.C.E
694
|
Posted - 2014.03.25 15:05:00 -
[2] - Quote
Roy Ventus wrote:Become a professional game programmer, test a patch on a test server, and then bring it up live and tell me if everything's super peachy. There's always bound to be issues, whether they're big or small.
I am a developer of scientific computational programs. I don't have millions of dollars. When I am given a deadline, and when I submit my code it works perfectly as intended. My codes go in pipelines for satellites that orbit the earth. It is entirely possibly to get things right on the first try. If I had this many errors in my codes I would be out of a job. If their test servers are not yielding the same results as the live servers then they absolutely need to fix their test servers because something is wrong.
On another note, how difficult is it to notice that too much HP was going to be a problem. Everyone saw it on the Dev blog from the excel table... People without PhDs saw it. People who didn't graduate high school saw it. Don't make excuses for incompetence.
Newb
|
Cenex Langly
D.A.R.K L.E.G.I.O.N
D.E.F.I.A.N.C.E
697
|
Posted - 2014.03.25 16:24:00 -
[3] - Quote
Marc Rime wrote:Uh, there are no major errors in that list. It's all just someone doing stuff in a hurry and making the odd mistake, it happens. Yeah, meticulously checking everything before release would have caught most of the mistakes, but that takes a *lot* of time. I'd rather they release stuff as quickly as possible, even if it means I have to live with a few items having bad values for a few days.codinge
No... Just no. Meticulously checking everything is good programming routine. In fact they say debugging is 80% of the coding process. If this is the case then they could have made all these changes in 2 weeks then spend the last 3 months making sure everything works properly.
What we are seeing is laziness, rushed work, and bad management. This is the most frustrating thing of anything in the coding process.
Bad coding would appear in the form of CCP Logibros response to tanks being fixed. He said they are trying to figure out how to fix tanks. He has no idea what the problem is, that is bad coding as there is nothing fixed yet because they don't know how to fix it.
Newb
|
|
|
| |
|