![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
pulling my hair out
Sep. 2nd, 2003 07:02 pmI'm still in hair pulling out mode over computer problems and not able to be online much, which has its upside, to be sure.
But hopefully I'll have DSL working TOMORROW, and if not, I am just going to send the whole mess back and get cable modem.
It's not rocket science, I know how to set it up, and it should just WORK, dammit, but of course it's not working.
After hassling with it, I get to the END of the on screen instructions, and it says something like, "If it doesn't work, be sure you're not trying to install it until AFTER the date on which you are supposed to have DSL connected." Well, that would be TOMORROW then, not today, so why not have that at the BEGINNING of the instructions?
Because a computer person wrote the instructions perhaps? I have a degree in computer science too, but I am also an editor, and one of jobs used to be taking software manuals and translating them into plain English so that my co-workers could use the instructions.
I would never put at the very END of a process something that the user should read FIRST. And this wasn't something I could have read on a piece of paper first - it was in the on screen installation process, so you had to go through all kind of crap to get to that point, where they THEN tell you to not try installing until the day AFTER you are supposed to start having the service.
What a stupid way to write a procedure.
But hopefully I'll have DSL working TOMORROW, and if not, I am just going to send the whole mess back and get cable modem.
It's not rocket science, I know how to set it up, and it should just WORK, dammit, but of course it's not working.
After hassling with it, I get to the END of the on screen instructions, and it says something like, "If it doesn't work, be sure you're not trying to install it until AFTER the date on which you are supposed to have DSL connected." Well, that would be TOMORROW then, not today, so why not have that at the BEGINNING of the instructions?
Because a computer person wrote the instructions perhaps? I have a degree in computer science too, but I am also an editor, and one of jobs used to be taking software manuals and translating them into plain English so that my co-workers could use the instructions.
I would never put at the very END of a process something that the user should read FIRST. And this wasn't something I could have read on a piece of paper first - it was in the on screen installation process, so you had to go through all kind of crap to get to that point, where they THEN tell you to not try installing until the day AFTER you are supposed to start having the service.
What a stupid way to write a procedure.