| Pages: [1] :: one page |
|
|
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
BL4CKST4R
WarRavens
League of Infamy
2516
   |
Posted - 2014.04.16 11:30:00 -
[1] - Quote
Title 2h/2l
For the Federation!
|
Korvin Lomont
United Pwnage Service
RISE of LEGION
918
|
Posted - 2014.04.16 11:32:00 -
[2] - Quote
BL4CKST4R wrote:Title 2h/2l
Jupp basicly ALL gallente BPO scout suits.
Valor is now 1/2 with one equip dren is the same like Dragonfly good work CCP *clap* CPU/PG seems also broken |
alten hilt
DUST University
Ivy League
221
|
Posted - 2014.04.16 11:36:00 -
[3] - Quote
I posted a thread over in the Technical Support/Bugs forum.
Making DUST 514 a Sandbox Shooter
|
shaman oga
Nexus Balusa Horizon
1870
|
Posted - 2014.04.16 11:43:00 -
[4] - Quote
DAMN!!!!
You force us to play in ADV.
Basic gal scout scout is 1/2 again......
FFFFF...............
CCP!!!!!!!
The unnamed new build it's so secret that nobody know what will be in it, even after patch notes..
\o/ summon me
|
Spectral Clone
Dust2Dust.
Top Men.
2257
|
Posted - 2014.04.16 12:01:00 -
[5] - Quote
You gotta be kidding me...
CCP GIT GUUD |
Pete B
Dogs of War Gaming
Zero-Day
141
|
Posted - 2014.04.16 12:21:00 -
[6] - Quote
Their all different. NEO-g1 has 1high 3low, G1 has 1high 2low, and my dragonfly has 2high 2low. |
BL4CKST4R
WarRavens
League of Infamy
2518
|
Posted - 2014.04.16 12:25:00 -
[7] - Quote
How does that even happen I am wondering...
For the Federation!
|
Spectral Clone
Dust2Dust.
Top Men.
2261
|
Posted - 2014.04.16 12:28:00 -
[8] - Quote
BL4CKST4R wrote:How does that even happen I am wondering...
Yes, how? |
Kristoff Atruin
Subdreddit
Test Alliance Please Ignore
2089
|
Posted - 2014.04.16 12:59:00 -
[9] - Quote
My guess is that either the scripts to fix these problems weren't checked in or the changes weren't made to the master copy of the database backup, depending on how they're doing deployments. Then a developer goes to change something else and runs the script to recreate all the stat tables or restores the updated backup file like he's supposed to, but it didn't include the last round of changes.
Every new project I've been on in the last 6 years has had problems with this kind of issue, and every time I've gone on a personal crusade to get other developers to stop making cowboy fixes and start following a process that makes this kind of situation impossible. But it's a change to how they work and a little bit of work up front that seems unnecessary until you've blown up an app in production and can't roll back to the previous state easily, so they almost always resist. |
Kasote Denzara
A Vulture
2279
|
Posted - 2014.04.16 13:32:00 -
[10] - Quote
Why does these things happen? Because it's Gallentean suits. Notice how there is never a fundamental issue like this with Caldari suits.
This is a signature. You have been enlightened.
|
|
|
Death Shadow117
Capital Acquisitions LLC
Dirt Nap Squad.
40
|
Posted - 2014.04.16 13:46:00 -
[11] - Quote
its bc ccp likes cal more
NOVA KNIVES WTF Are Those
|
Joel II X
Dah Gods O Bacon
2309
|
Posted - 2014.04.16 14:01:00 -
[12] - Quote
CCP hates Gallente. |
REDBACK96USMC
Molon Labe.
General Tso's Alliance
7
|
Posted - 2014.04.16 14:13:00 -
[13] - Quote
Kristoff Atruin wrote:My guess is that either the scripts to fix these problems weren't checked in or the changes weren't made to the master copy of the database backup, depending on how they're doing deployments. Then a developer goes to change something else and runs the script to recreate all the stat tables or restores the updated backup file like he's supposed to, but it didn't include the last round of changes.
Every new project I've been on in the last 6 years has had problems with this kind of issue, and every time I've gone on a personal crusade to get other developers to stop making cowboy fixes and start following a process that makes this kind of situation impossible. But it's a change to how they work and a little bit of work up fr. ont that seems unnecessary until you've blown up an app in production and can't roll back to the previous state easily, so they almost always resist.
Well I would consider a better class of programmers to work with. :-p I can recount horror story after story of people and projects like this. It is obvious CCP needs a good lead and firm processes. Proof is in the pudding.
|
AREYOUTHAT STUPID
Carbon 7
Iron Oxide.
34
|
Posted - 2014.04.16 14:15:00 -
[14] - Quote
Could we get an official CCP response on this? This was hotfix'd after 1.8 dropped so I am assuming it will be an easy fix. Being proactive and posting an official response will help with fielding tons of these type of emails.
Consumer of bacon flavored proto tears
|
Kristoff Atruin
Subdreddit
Test Alliance Please Ignore
2091
|
Posted - 2014.04.16 14:19:00 -
[15] - Quote
REDBACK96USMC wrote:Kristoff Atruin wrote:My guess is that either the scripts to fix these problems weren't checked in or the changes weren't made to the master copy of the database backup, depending on how they're doing deployments. Then a developer goes to change something else and runs the script to recreate all the stat tables or restores the updated backup file like he's supposed to, but it didn't include the last round of changes.
Every new project I've been on in the last 6 years has had problems with this kind of issue, and every time I've gone on a personal crusade to get other developers to stop making cowboy fixes and start following a process that makes this kind of situation impossible. But it's a change to how they work and a little bit of work up fr. ont that seems unnecessary until you've blown up an app in production and can't roll back to the previous state easily, so they almost always resist. Well I would consider a better class of programmers to work with. :-p I can recount horror story after story of people and projects like this. It is obvious CCP needs a good lead and firm processes. Proof is in the pudding.
Hah, well it isn't like I have much of a choice...the industry is packed with developers like this. I work for a consulting firm so I get to see inside a lot of different places and it's all the same everywhere. Once I had this app that our company had built from the ground up for a government department, and after years of maintenance and upgrades was being handed off to a new team. I literally spent hours trying to convince them of the value of source control combined with a build server. Hours! They didn't even have to set anything up, the servers and configs were already in place...all they had to do was keep following the process of adding a folder for the current build number, creating db change scripts and then grabbing the deployment zip file from the dev server. It was a process we had put in place so that a non-developer could do the actual deployment and, if something got mucked up, we could revert the whole thing in 10 minutes by grabbing a previous deployment zip and giving it to the dba or support monkey who was working at the time.
Supposedly despite the fact that I've barely written more than a dozen lines of actual code in almost two years, understanding this makes me a "good" developer heh. |
Dheez
Kinsho Swords
Caldari State
91
|
Posted - 2014.04.16 14:56:00 -
[16] - Quote
Kristoff Atruin wrote:My guess is that either the scripts to fix these problems weren't checked in or the changes weren't made to the master copy of the database backup, depending on how they're doing deployments. Then a developer goes to change something else and runs the script to recreate all the stat tables or restores the updated backup file like he's supposed to, but it didn't include the last round of changes.
Every new project I've been on in the last 6 years has had problems with this kind of issue, and every time I've gone on a personal crusade to get other developers to stop making cowboy fixes and start following a process that makes this kind of situation impossible. But it's a change to how they work and a little bit of work up front that seems unnecessary until you've blown up an app in production and can't roll back to the previous state easily, so they almost always resist.
CCP = Condones Crappy Programming, Collects Chump Programmers
|
|
|
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |