![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
seldearOkay, panic time.
Work has just announced that we're moving all stable developments to our Quality system. This Friday.
Sheeeeeeesh.
For those of you who don't know (and do care) how system development works, most computer systems I've worked on have a three-tier system: Development (Dev), Quality Assurance (QA), and Production (Prod).
Development is for exactly that: developing new functionality (eg. a report on how many units of material we've sold this month). It usually has a lot of mocked-up or fake data in it. eg. Employee names will be things like Minnie Mouse, who's married to Mickey, and Mickey is the supervisor of Donald Duck. We usually do some basic testing in the Dev system: enough to get the feel for whether what we're developing seems to work as it should.
Once we have an idea if it works or not, the new function is moved up to QA.
Quality Assurance is to test the development with data that's a little closer to being 'real' than the Dev system has. Ideally, it's also free of all the little 'test' modifications that people make without thinking about in Dev, so often you'll find things in QA don't work the same way they do in Dev.
And Prod is the real-time, real-system, you-break-it-you-bought-it system. Screw this up and your employment prospects become measured in days, if not hours.
And we're moving just about everything in our Dev system up to QA on Friday. All at once, instead of one development at a time.
Next Monday is going to be insane.
And I have Big Bang to write!!
I may need a tag called 'AAAAUUUGH!'
Work has just announced that we're moving all stable developments to our Quality system. This Friday.
Sheeeeeeesh.
For those of you who don't know (and do care) how system development works, most computer systems I've worked on have a three-tier system: Development (Dev), Quality Assurance (QA), and Production (Prod).
Development is for exactly that: developing new functionality (eg. a report on how many units of material we've sold this month). It usually has a lot of mocked-up or fake data in it. eg. Employee names will be things like Minnie Mouse, who's married to Mickey, and Mickey is the supervisor of Donald Duck. We usually do some basic testing in the Dev system: enough to get the feel for whether what we're developing seems to work as it should.
Once we have an idea if it works or not, the new function is moved up to QA.
Quality Assurance is to test the development with data that's a little closer to being 'real' than the Dev system has. Ideally, it's also free of all the little 'test' modifications that people make without thinking about in Dev, so often you'll find things in QA don't work the same way they do in Dev.
And Prod is the real-time, real-system, you-break-it-you-bought-it system. Screw this up and your employment prospects become measured in days, if not hours.
And we're moving just about everything in our Dev system up to QA on Friday. All at once, instead of one development at a time.
Next Monday is going to be insane.
And I have Big Bang to write!!
I may need a tag called 'AAAAUUUGH!'
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2009-09-14 09:28 am (UTC)As a fellow ITer and someone who went through similar madness during 1999-2000 (including a 22-hour workday), I sympathise.
All the best - and stay sane :)
no subject
Date: 2009-09-14 02:41 pm (UTC)no subject
Date: 2009-09-14 08:51 pm (UTC)no subject
Date: 2009-09-14 08:52 pm (UTC)Thanks. *wry smile*
no subject
Date: 2009-09-15 12:49 am (UTC)