ahead
Note: all references to "Indian" here refer to nationality, not ethnicity. Indian-Americans seem to be magically exempt from the case I outline below.
Anyone who's worked with an Indian student on any kind of project can probably agree with me that, while they're fantastic test-takers, they generally fail at critical thinking and design. If it's not a process they can memorize and reproduce with little or no alteration of the original steps, they're going to struggle with it. In every single software engineering presentation I have seen or participated in, the non-Indians (this includes non-Indian Asians and foreign students from the Middle East and Europe) have, on the average, been capable producers.
We got a new guy on my team a month ago. He is Indian - got his bachelor's in EE in India and his master's in CS. Okay. Well, maybe the Indians at my school were incompetent, and they were the exception to the rule. A very concentrated exception to the rule.
This guy...
I want to throttle him. I can tell him one thing, ask him to confirm that he understands it, and, less than a day later, he'll have forgotten it. If it isn't a cookie-cutter design that he can write down on a pad of paper, he doesn't understand it. Let's start with some of his gems:
"when u say richard michaels and i say bob matthews r u referring to the same person?"
"is a change request the same thing as a service request?"
(Keep in mind, he spent a month in training discussing issues like these before working on our team)
As I'm talking him through one of our software's process over IM...
Fifteen minutes into it...
Me: "So, on the left, you should see a button that says 'Code Review'. Do you see it?"
Him: "no"
Me: "Why?"
Him: "i culdn't log in"
His grasp of sentence flow is fantastic, too. A software engineer e-mailed him and said, "Is it safe to run this failed script?"
His reply? "Go ahead and run the script and I don't know why it failed."
Please note that everything after "and" was taken from what I said in an IM conversation.
I have to dictate his e-mails for him. Why? Because he can't. His terrible grasp of sentence flow and structure aside, he won't learn the material. He writes something, and I explain that it's wrong and why[/b] it's wrong. I ask if he understands it, and he says yes. I tell him a better way to word it. He rewrites it, and, in the five seconds between my saying it and it being typed, he horribly maligns it.
And, for a longer example, yesterday he received the following request:
A very simple request. I tell him that he will need to use the template script we have on our team share. I show where our document templates are. Now, the hardest part of this is the documentation, as it's not exactly clear about what goes where. So, I take the documentation for an earlier project that dropped another index and said to use the documentation as a basis (and I sent him the documentation).
He sends me his first draft. Okay, not bad. I tell him what template leftovers need to be removed, what he missed, and send it back to him. He sends it back, having removed all I told him - and copied over the document I sent to him as a basis into the new document. So, to make this clear: he took a document from a completely different project, copied its contents into this new project, and didn't understand why that didn't work. So, I politely told him why it wasn't right. He finally fixed it on the third time around.
At this point, I inform him that he will now need to implement the template (which I had informed him to do the previous day). I told him it's on the share (again) and that, once he had finished that, he should send the script and the documents out to the team for review.
Five minutes later, I get an e-mail from him to the entire team asking for us to review the documents. There is no script attached. I inquire to the script, and he says, "o yah, is there a template i can use?"
:smack: At this point, I'm getting pissed off, so I tell him, "Yes, as I said above, it's on the share. Implement that and then send out the documents again." I left work at that point.
Beyond this one story, he routinely writes code without understanding what it's doing. You tell him, "Implement this query into the script in the same way that it's implemented on line 23 of that same script." He can't do this. I tell him to learn some code and figure out what it's doing. I ask if he understands it, and he says yes. If I ever ask him to walk me through his code, he can't.
tl;dr: Indians suck.
Note: all references to "Indian" here refer to nationality, not ethnicity. Indian-Americans seem to be magically exempt from the case I outline below.
Anyone who's worked with an Indian student on any kind of project can probably agree with me that, while they're fantastic test-takers, they generally fail at critical thinking and design. If it's not a process they can memorize and reproduce with little or no alteration of the original steps, they're going to struggle with it. In every single software engineering presentation I have seen or participated in, the non-Indians (this includes non-Indian Asians and foreign students from the Middle East and Europe) have, on the average, been capable producers.
We got a new guy on my team a month ago. He is Indian - got his bachelor's in EE in India and his master's in CS. Okay. Well, maybe the Indians at my school were incompetent, and they were the exception to the rule. A very concentrated exception to the rule.
This guy...
I want to throttle him. I can tell him one thing, ask him to confirm that he understands it, and, less than a day later, he'll have forgotten it. If it isn't a cookie-cutter design that he can write down on a pad of paper, he doesn't understand it. Let's start with some of his gems:
"when u say richard michaels and i say bob matthews r u referring to the same person?"
"is a change request the same thing as a service request?"
(Keep in mind, he spent a month in training discussing issues like these before working on our team)
As I'm talking him through one of our software's process over IM...
Fifteen minutes into it...
Me: "So, on the left, you should see a button that says 'Code Review'. Do you see it?"
Him: "no"
Me: "Why?"
Him: "i culdn't log in"
His grasp of sentence flow is fantastic, too. A software engineer e-mailed him and said, "Is it safe to run this failed script?"
His reply? "Go ahead and run the script and I don't know why it failed."
Please note that everything after "and" was taken from what I said in an IM conversation.
I have to dictate his e-mails for him. Why? Because he can't. His terrible grasp of sentence flow and structure aside, he won't learn the material. He writes something, and I explain that it's wrong and why[/b] it's wrong. I ask if he understands it, and he says yes. I tell him a better way to word it. He rewrites it, and, in the five seconds between my saying it and it being typed, he horribly maligns it.
And, for a longer example, yesterday he received the following request:
Quote:
I need a script that will drop index A from table B.
A very simple request. I tell him that he will need to use the template script we have on our team share. I show where our document templates are. Now, the hardest part of this is the documentation, as it's not exactly clear about what goes where. So, I take the documentation for an earlier project that dropped another index and said to use the documentation as a basis (and I sent him the documentation).
He sends me his first draft. Okay, not bad. I tell him what template leftovers need to be removed, what he missed, and send it back to him. He sends it back, having removed all I told him - and copied over the document I sent to him as a basis into the new document. So, to make this clear: he took a document from a completely different project, copied its contents into this new project, and didn't understand why that didn't work. So, I politely told him why it wasn't right. He finally fixed it on the third time around.
At this point, I inform him that he will now need to implement the template (which I had informed him to do the previous day). I told him it's on the share (again) and that, once he had finished that, he should send the script and the documents out to the team for review.
Five minutes later, I get an e-mail from him to the entire team asking for us to review the documents. There is no script attached. I inquire to the script, and he says, "o yah, is there a template i can use?"
:smack: At this point, I'm getting pissed off, so I tell him, "Yes, as I said above, it's on the share. Implement that and then send out the documents again." I left work at that point.
Beyond this one story, he routinely writes code without understanding what it's doing. You tell him, "Implement this query into the script in the same way that it's implemented on line 23 of that same script." He can't do this. I tell him to learn some code and figure out what it's doing. I ask if he understands it, and he says yes. If I ever ask him to walk me through his code, he can't.
tl;dr: Indians suck.
the idiot is the person who follows the idiot and your not following me your insulting me your following the path of a idiot so that makes you the idiot - LC Tusken