![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
So frustrated.
Network guy thinks entirely too literal.
We're doing a file transfer from one system to another, entirely different companies, boxes, the whole shemozzle. I asked the network guy for a userid/password for the other system to FTP the file over to the directory where my program is going to check for it, so it can pick it up and process it in our system.
I sent him the literal directory name as my system/program understands it, because I didn't know the IP address, or the term he uses for "an FTP directory in which they're going to put incoming files for the SAP system".
His response?
"Why does she have to access it from her desktop? What is the obsession you have with accessing files from the desktop?"
The mail, BTW, had all the background about the connection between the two systems and the actual interface process. If he'd had half a brain cell, he would have realised the context is transferring a file from one system to the next, requiring an FTP transfer from them to us, which needs:
1. a directory for them to put the file in
2. a username and password to access the directory from their system
Why is this so hard for him to understand? It's like he's being deliberately stupid. Which wouldn't surprise me; this guy is not exactly the brightest bulb in chandelier.
And this is why I would never want to be a manager (as discussed in a conversation with some co-workers yesterday). The truth is that I have enough trouble dealing with 'stupid people' as a programmer. I should hate to have to deal with stupid people ALL THE TIME as a project manager or team leader.
Hell to the no.
(ps. this is going to be the shape of things for the day, I suspect. I'm going to rant on here because there's not really anywhere else to rant.)
Network guy thinks entirely too literal.
We're doing a file transfer from one system to another, entirely different companies, boxes, the whole shemozzle. I asked the network guy for a userid/password for the other system to FTP the file over to the directory where my program is going to check for it, so it can pick it up and process it in our system.
I sent him the literal directory name as my system/program understands it, because I didn't know the IP address, or the term he uses for "an FTP directory in which they're going to put incoming files for the SAP system".
His response?
"Why does she have to access it from her desktop? What is the obsession you have with accessing files from the desktop?"
The mail, BTW, had all the background about the connection between the two systems and the actual interface process. If he'd had half a brain cell, he would have realised the context is transferring a file from one system to the next, requiring an FTP transfer from them to us, which needs:
1. a directory for them to put the file in
2. a username and password to access the directory from their system
Why is this so hard for him to understand? It's like he's being deliberately stupid. Which wouldn't surprise me; this guy is not exactly the brightest bulb in chandelier.
And this is why I would never want to be a manager (as discussed in a conversation with some co-workers yesterday). The truth is that I have enough trouble dealing with 'stupid people' as a programmer. I should hate to have to deal with stupid people ALL THE TIME as a project manager or team leader.
Hell to the no.
(ps. this is going to be the shape of things for the day, I suspect. I'm going to rant on here because there's not really anywhere else to rant.)