Tweet
Ok, where I work, we use the Agile development methodology. For those who don't know what that means, we have very short development cycles.
Before we started on this one project, we were on three-week iterations. This means we basically had two weeks to develop (i.e. write code) and a week for bug fixes.
Since this project started, we've dropped to TWO week iterations. Meaning now we only have ONE week to develop and one week for bug fixes/QA.
And for some reason, those higher up the food chain than the developers sometimes decide to change things in the middle of our development cycle.
Well, today, a guy was trying to make a change to a database table. Instead of possibly doing it the way he should have, he took it a different way. Well, he apparently wrote the script wrong, and where the script was supposed to insert the records, it failed, and just continued on ward.
He did no error checking.
The problem is, a few commands later was a DROP TABLE command...
Which removed the table we needed...along with all it's data.
Before we started on this one project, we were on three-week iterations. This means we basically had two weeks to develop (i.e. write code) and a week for bug fixes.
Since this project started, we've dropped to TWO week iterations. Meaning now we only have ONE week to develop and one week for bug fixes/QA.
And for some reason, those higher up the food chain than the developers sometimes decide to change things in the middle of our development cycle.
Well, today, a guy was trying to make a change to a database table. Instead of possibly doing it the way he should have, he took it a different way. Well, he apparently wrote the script wrong, and where the script was supposed to insert the records, it failed, and just continued on ward.
He did no error checking.
The problem is, a few commands later was a DROP TABLE command...
Which removed the table we needed...along with all it's data.
Comment