Work sucks, funny sounds
Dec. 19th, 2002 11:33 pmThose of you who interacted with me online over the last couple of days may have noticed that I've been a little bitchy. More so than usual, that is. :-)
That was because the place where I worked released a product that I was working on yesterday. 14,000 lines of code, hardly trivial. Now, in the software industry, there are normally these things written called "Technical Specifications", which describe how a product is supposed to work in detail. That way, all of the specs can be written in advance, and then the programmer (me) can spend several days/weeks building it, without having to stop and ask his boss (or the customer) questions every 5 minutes. It's like a "road map" for software development; if I have one, I don't have to stop and ask for directions. Plus, when the product gets released, it will behave exactly like the customer expected it to work.
Everyone got that so far? Good, because that's how it is SUPPOSED to work.
The way it happens at where I work is a little different. My boss "doesn't have the time to write specs". This means that when a product is released, it doesn't work the exact way that he expected it to work, and now I'm forced to debug a product that is live and accepting (or rejecting, based on the bug) orders, and potentially costing the company money in lost sales. Not good. Having to fix bugs under these conditions is VERY stressful. It also forces me to stay late, to the tune of 10 PM at night or later. Not very good for employee morale, either. And yes, the time spent debugging the system and fixing screwed up orders is a multiple of the time that it would have taken to write specs in the first place.
So that's what I was doing the last 2 days. It's why I'm completely stressed out, pissed off, and upset.
In other news,
javu made some funny sounds for me today. I have them up in my webspace at http://www.members.dca.net/dmuth/sounds/.
xydexx also made some really funny comments on FurryMUCK, which got me to laugh and brightened today just a little. Thanks guys. :-)
Finally, I shaved my head again tonight. It was easier this time around, and my scalp doesn't feel nearly as sensitive as the first time I shaved it.
That was because the place where I worked released a product that I was working on yesterday. 14,000 lines of code, hardly trivial. Now, in the software industry, there are normally these things written called "Technical Specifications", which describe how a product is supposed to work in detail. That way, all of the specs can be written in advance, and then the programmer (me) can spend several days/weeks building it, without having to stop and ask his boss (or the customer) questions every 5 minutes. It's like a "road map" for software development; if I have one, I don't have to stop and ask for directions. Plus, when the product gets released, it will behave exactly like the customer expected it to work.
Everyone got that so far? Good, because that's how it is SUPPOSED to work.
The way it happens at where I work is a little different. My boss "doesn't have the time to write specs". This means that when a product is released, it doesn't work the exact way that he expected it to work, and now I'm forced to debug a product that is live and accepting (or rejecting, based on the bug) orders, and potentially costing the company money in lost sales. Not good. Having to fix bugs under these conditions is VERY stressful. It also forces me to stay late, to the tune of 10 PM at night or later. Not very good for employee morale, either. And yes, the time spent debugging the system and fixing screwed up orders is a multiple of the time that it would have taken to write specs in the first place.
So that's what I was doing the last 2 days. It's why I'm completely stressed out, pissed off, and upset.
In other news,
Finally, I shaved my head again tonight. It was easier this time around, and my scalp doesn't feel nearly as sensitive as the first time I shaved it.
*squeaks for you*
Re: *squeaks for you*
Date: 2002-12-20 02:37 am (UTC)ACK! *legs it*
buckets and buckets
Date: 2002-12-20 03:42 pm (UTC)(no subject)
Date: 2002-12-19 11:09 pm (UTC)Heh.
Date: 2002-12-20 03:44 am (UTC)(no subject)
Date: 2002-12-20 11:15 am (UTC)(no subject)
Date: 2002-12-20 10:23 am (UTC)You've worked at a place that's actually done that? ;)
(no subject)
Date: 2002-12-20 10:29 am (UTC)