![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Monday, July 21st, 2008 10:22 am
it's totally a monday
I knew it was a Monday when I woke up, sure. But do Mondays have to be so...so Mondayish? I mean, it's a cliche--everything is not really supposed to go wrong on Monday! And why my life thinks it's supposed to is a mystery I am sure I will never solve.
And if this program doesn't stop screwing around I will not snap, per se, but I will finally admit I snapped a long, long time ago and stop trying to control homicidal impulses, because really. Sure, jail time, but on the other hand--okay, I don't have another hand for this one.
What I have learned:
1.) Programmers should not be allowed near programs without adequate supervision. Before you look at me like I'm nuts (even though, yeah, there is that), we have yet another improvement to the system that miraculously makes an already confusing method of inquiry even more confusing by changing a nice single page into a series of a million much shorter pages. I wish I could really get across the full extent of the nightmare that has become my life, but imagine trying to read a fic with six words per page, but pretend the word is a case number and you are supposed to sort all the cases by date, but you can't because the cases are now all on different pages and there is no way to sort them. And there are different types of words, or cases, rather, and you just stare at it and then ask your boss for the developer's name and ten minutes in the break room no questions asked.
Why did they think this was a good idea?
2.) I'm freaking serious about the break room. I only need five and a blue pen.
3.) I'd settle for two minutes and anthrax.
4.) This problem is exacerbated by the fact I don't think any of the programmers have any idea of what they are actually writing. Bear with me. They are each given a small module of a much, much, much larger program, and I get the distinct impression they aren't really aware that there is a larger program. They also really do not understand who they are writing for. I used to hear the arguments they'd make against stuff we wanted the program to do that were kind of insane. I mean, insane.
5.) Only one of five can document.
6.) Of those one in five, none of them speak English as a first language (or second, for that matter), so there's a lot of interpretation between technical speak and layman English with a lot of inquiries into if they speak American English or British English, because wow, can that go tragic places fast. It's not even the language barrier--a huge amount of it is the technical language barrier--I don't think many of them really absorbed How To Talk to the Layman About Hideously Complicated Changes That Make No Sense.
7.) This design is still hideous. Inline frames do not make things better.
8.) One minute and ebola. Just one.
*sighs*
I'm hunting up every h/c dS fic I have read, create a list, and re-read it all when I get home. Maybe SGA too. Something with Rodney and a crushed hand, maybe.
And if this program doesn't stop screwing around I will not snap, per se, but I will finally admit I snapped a long, long time ago and stop trying to control homicidal impulses, because really. Sure, jail time, but on the other hand--okay, I don't have another hand for this one.
What I have learned:
1.) Programmers should not be allowed near programs without adequate supervision. Before you look at me like I'm nuts (even though, yeah, there is that), we have yet another improvement to the system that miraculously makes an already confusing method of inquiry even more confusing by changing a nice single page into a series of a million much shorter pages. I wish I could really get across the full extent of the nightmare that has become my life, but imagine trying to read a fic with six words per page, but pretend the word is a case number and you are supposed to sort all the cases by date, but you can't because the cases are now all on different pages and there is no way to sort them. And there are different types of words, or cases, rather, and you just stare at it and then ask your boss for the developer's name and ten minutes in the break room no questions asked.
Why did they think this was a good idea?
2.) I'm freaking serious about the break room. I only need five and a blue pen.
3.) I'd settle for two minutes and anthrax.
4.) This problem is exacerbated by the fact I don't think any of the programmers have any idea of what they are actually writing. Bear with me. They are each given a small module of a much, much, much larger program, and I get the distinct impression they aren't really aware that there is a larger program. They also really do not understand who they are writing for. I used to hear the arguments they'd make against stuff we wanted the program to do that were kind of insane. I mean, insane.
5.) Only one of five can document.
6.) Of those one in five, none of them speak English as a first language (or second, for that matter), so there's a lot of interpretation between technical speak and layman English with a lot of inquiries into if they speak American English or British English, because wow, can that go tragic places fast. It's not even the language barrier--a huge amount of it is the technical language barrier--I don't think many of them really absorbed How To Talk to the Layman About Hideously Complicated Changes That Make No Sense.
7.) This design is still hideous. Inline frames do not make things better.
8.) One minute and ebola. Just one.
*sighs*
I'm hunting up every h/c dS fic I have read, create a list, and re-read it all when I get home. Maybe SGA too. Something with Rodney and a crushed hand, maybe.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
From:I've requested a meeting with X tomorrow. Maybe if we sit there together and I actually supervise her, we can get at least a few meetings set up, so we won't be too desperately behind schedule. I also plan to get a set of questions firmed up so that we can keep the meetings with [Pit Of Vipers staff] as short, direct, and to the point as possible, since we're so far behind where we should be.
Also, X has not to my knowledge done any of the online training provided by our Document Management System, nor has she read any of the document management information I have provided to her. She seems unable to comprehend the function of keywords, search terms, and the autofill requirements and functions. As a co-project manager she insists on being involved in every step, but I feel her complete lack of knowledge of this system, and even of how any document management system is supposed to work, is going to be a more serious problem the closer we get to rollout and implementation.
Good times, good times. Please share the H/C list if and when you finalize it? It's a very Mondayish Monday indeed.
(- reply to this
- thread
- link
)
no subject
From:http://squidge.net/dsa/archive/3/busted.html
Current h/c reading. It also has a sequel, so it is like h/c Christmas.
(- reply to this
- parent
- thread
- top thread
- link
)
no subject
From:\o/
Oh, god, "Busted" is just about my favorite h/c story ever, ever. And I haven't read it in SO LONG. Thank you thank you! I am going to read it during lunch, and it will make me feel better, and that will be greatness. *G*
(- reply to this
- parent
- thread
- top thread
- link
)
no subject
From:Me and my list are as one today.
(- reply to this
- parent
- thread
- top thread
- link
)
no subject
From:Finding the Words...no, I don't believe I have! If it's a story about Ray's aphasia, I will hug it to bits and love it and kiss it and call it George. Heeee.
(- reply to this
- parent
- thread
- top thread
- link
)
no subject
From:You might have read it already. It's a *lot* of h/c.
(- reply to this
- parent
- thread
- top thread
- link
)
no subject
From:(- reply to this
- parent
- top thread
- link
)