![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Entry tags:
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.
no subject
So the program is really like The Cube?
no subject
This?
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
Re: Cube
(Anonymous) - 2008-07-21 16:51 (UTC) - Expandno subject
A language barrier PLUS a technical language barrier... *shudders* We're here for you.
no subject
A language barrier PLUS a technical language barrier... *shudders* We're here for you.
The rare written documentation is like having a very strange case of visual aphasia or something. I know they have to mean to use other words, but God knows what that was supposed to be.
no subject
They feed you. And I figure you can get quite a bit of reading done.
(Not only is it Monday, but I am 46 years old, and I am entering day 37 of this particular cycle, which means that I have been heavily premenstrual for something like three weeks now. I. am. dying. And I have no idea why WordPress recognizes that it's on the home page once in this sidebar script and then does not recognize the exact same condition about 30 lines of code later. But it let me set a flag the first time, and it recognizes the flag when I need it to, so good enough. I am reaching the, "I just don't care anymore," point in this project.) (Jesus Christ.)
no subject
And ooh. *winces for you* Okay, your day may be worse. Depending on if I get my thirty seconds with the breakroom and a pointy object.
no subject
I need to stop there, because ranting will not help. I just...I get it, and I'm really deeply sorry.
no subject
no subject
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.
no subject
http://squidge.net/dsa/archive/3/busted.html
Current h/c reading. It also has a sequel, so it is like h/c Christmas.
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
no subject
no subject
no subject
Imagining torture can be soooo satisfying . . .
Feel free to update and embellish as desired. :)
no subject
(no subject)
(no subject)
no subject
no subject
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.
See, this is what frustrates me about my job search. I'm a computer science major (BS from the College of Engineering) with a minor in English. I've been working in this goddamned field for (holy crap!) 15 years now. I write both project design documents and custom software applications to make people weep. I've made Microsoft Office my bitch.
And yet no one wants to hire me.
Um, yeah, so translate all that whining to "I feel your pain", truly.
no subject
(no subject)
(no subject)
no subject
no subject
no subject
You get one out of five to document? That's magical!!! (And I'm not even talking about user documentation of which we have none here. We used to have someone who did that full time but layoffs of 2002 put an end to that and never brought it back.) I'm just talking about documenting the code so other programmers can pick up the slack.
no subject
And I hear you on user doc--the testers (aka my unit), are basically writing the documentation ourselves by guessing what we think the change is and what we *think* its supposed to do. It's--well. Hellish.
(no subject)
Geek-to-English Translation
Every programmer in the English-speaking world, EVERY single one, should have to take at least one class on Geek-to-English Translation. I am both a programmer and a trained technical writer (actually took university classes for exactly that), and the skill that got me my very first post-university job - and made the developers love me - was my ability to translate Geekspeak into layman's English (so they didn't have to do it).
Also? Programmers, myself included, have a tendency - a very strong tendency - to implement things because they can. This feature would be so cool! What? No, I don't know if the users need it, but it would be so cool! I'ma implement it and they'll all just love it. Look! It knocks out seven hundred lines of code in this module and I only have to add three hundred lines of code to this module! Documentation? Ummm... we don't have the budget or the schedule for documentation. This is easy to use, right? I mean, it makes sense to me...
We used to call it "Oooh, Shiny! Syndrome". =)
On the other hand, one of my university professors (in the Computer Science department) had a degree in English (or perhaps Journalism?), and would bounce projects if there were typos or grammatical errors in one's comments. For that matter, he would bounce projects if the comments did not meet his very specific, very detailed commenting guidelines. As students, we hated that; as professionals in the workplace, we sure as hell appreciate it, now.
People who haven't been taught the pitfalls of documentation don't even think about things like avoiding jargon and slang, spelling out TLAs (three-letter acronyms) or proof-reading for typos and missing/misused words. Every programmer who works with English-speaking users needs a Geek-to-English translator.
And every "enhancement" needs a kill switch. ;)
Re: Geek-to-English Translation
Re: Geek-to-English Translation
Re: Geek-to-English Translation
Re: Geek-to-English Translation
Re: Geek-to-English Translation
Re: Geek-to-English Translation
Re: Geek-to-English Translation
Re: Geek-to-English Translation
no subject
no subject
Have you read Northern Light (http://www.benandrayk.com/shadow/northern.htm) by Shadow? Or
no subject
no subject
*offers*
no subject
And yes, this has been completely and utterly a Monday. It's been a series of irritations and minor disasters for every single person I've talked to today.