Indian IT consultancies struggle against technological obsolescence
131–140 of 285 posts
Re: Indian IT consultancies struggle against technological obsolescence
#132Earlier quoted context omitted.
Wrong—“codes” is correct in the Indian dialect of English. This is akin to arguing over whether “color” or “colour” is the correct spelling.
While what I'll say will surely be controversial and will lead to many down votes, Indian dialect of English is not considered a "standard." As a result, the correctness of something in Indian dialect does not mean it is "proper English" or "correct English". If you go to non-English speaking Europe, most textbooks come from the British Council, and teach British English. If you go to China and a lot of Asian countri…
Linguistic prescriptivism is just class oppression by another name. As long as language can be understood it can't be wrong. Intelligibility is what matters, not if someone subscribes to the particulars of a given style guide. Saying otherwise just serves to suppress the voices of people who speak other dialects.
Re: Indian IT consultancies struggle against technological obsolescence
#133Thanks. Grammar check - its note "codes"; it is "code".
We detached this subthread from https://news.ycombinator.com/item?id=23942095.
Re: Indian IT consultancies struggle against technological obsolescence
#134Thanks. Grammar check - its note "codes"; it is "code".
Wrong—“codes” is correct in the Indian dialect of English. This is akin to arguing over whether “color” or “colour” is the correct spelling.
The great grandparent's post is more difficult to read than it otherwise would be to the vast majority of HN users who use other English dialects.
American, Australian, German, British, etc. English are all mutually intelligible with no difficulty, while the... *counts... 11 deviations from the more common (as determined by looking at HN posters) grammars in the great grandparent require a bit of work on the part or the reader.
Re: Indian IT consultancies struggle against technological obsolescence
#135Earlier quoted context omitted.
I see nothing wrong or nonstandard with Indian English, as a native US English speaker living in Canada myself. Are you going to claim that Canada uses nonstandard English simply because it's a hybrid of US and UK English with a few phonetic and lexical twists of its own? Or that Scottish English is somehow less legitimate than England's English (the two are quite different) despite Scotland being part of the UK for…
> I see nothing wrong or nonstandard with Indian English, as a native US English speaker living in Canada myself. I try to see it from the perspective of a non-native speaker trying to learn English. If I know no English, and pay for teachers to teach me English, I definitely do not want to be taught Indian English. Not because it's wrong, not because it's $whatever_adjective, but because it will sound incorrect to t…
I want to point out your claim about 'majority of English speakers'. The number of English speakers in the Indian subcontinent is much higher than anywhere else in the world, including US.
Source : https://en.wikipedia.org/wiki/List_of_countries_by_English-s...
If numbers decide what is the norm, Indian English should be it. However, I feel like there are other factors that you are using to determine the "correct" English.
Re: Indian IT consultancies struggle against technological obsolescence
#136I recently joined a company where my main task is to modernise a business critical application built and supported by Wipro over ten years ago. Everything is still on .Net 3.0 (first released in 2007), and despite hundreds of pages of documentation the developers seem to have little understanding of what the application actually does for the business. The impression I have is that their business model is geared towar…
Of course. Most manager types assume all code monkeys are the same. They just turn a crank all day. In the end one of the other key factors is just monthly expense. Business types like locking in engineering costs at $XX,000 per month. They have no ability to see that they will be paying twice as long until feature Y is ready and even then it won't be what they really want. But they did cut $30K from the monthly engineering expenses so here is a 10% raise and a bonus. Great Job!!!
Re: Indian IT consultancies struggle against technological obsolescence
#137This feeble attempts to generalize a whole nation or group of people will not succeed. Individuals differ from one another and Indians are the most diverse group in the world. Some of the engineers are good some are bad , just like everywhere else. The sooner humanity realizes the truth about individuality and discard the stereotypes attached to groups and aggregates the better it will be for the whole world. Amen.
> and Indians are the most diverse group in the world What metric(s) are you using to measure that diversity? I live in Toronto, Canada, and approximately 50% of residents here were born overseas. Toronto likes to boast it is one of the most diverse cities in the world (based on that metric, at least).
They're probably using this list
https://en.wikipedia.org/wiki/List_of_countries_ranked_by_et...
And you are probably using this one
https://en.wikipedia.org/wiki/List_of_sovereign_states_and_d...
So it depends what you mean by diversity
Re: Indian IT consultancies struggle against technological obsolescence
#138Earlier quoted context omitted.
Adding to this. I've worked with people from Tech Mahindra. Some observations. 1. Very green staff that have little to no coding skills/ability. 2. Communication barriers, even when the people are local. 3. Jobs that any other organization would do with one person being split into 3 different roles with a net result of costing more than hiring the more expensive onshore devs. 4. Because of #3 software takes longer to…
> Jobs that any other organization would do with one person being split into 3 different roles with a net result of costing more than hiring the more expensive onshore devs When I first started working with an offshore team of Capgemini devs back around 2007, this really struck me too. It was bizarre - you had "devs" who literally knew nothing beyond their very limited task space. Literally.nothing. You'd have 3 peop…
Yes, their job is to Bill Hours, so if they're working an inefficient process* or dealing with a bad architecture that needs all hands on deck to deploy anything or the developers environment takes ten minutes to go from edit->compile->debug, none of them are going to raise their hand and call out this bullshit, especially if they're new to the team or new to the business.
* a config flag needs to be changed for a new release. Configs are stored in a database. A dev needs to write a SQL update script to make the change. This needs to go through QA, and be signed off by a DBA.
Re: Indian IT consultancies struggle against technological obsolescence
#139Thanks. Grammar check - its note "codes"; it is "code".
Wrong—“codes” is correct in the Indian dialect of English. This is akin to arguing over whether “color” or “colour” is the correct spelling.
Most of the time Indian developers are working with American or European clients. I have seen multiple situations where non Indians make fun of and devalue contributions by Indian developers because they use phrases like codes , needful and revert. Just avoid using these phrases. There are other battles to fight.
Re: Indian IT consultancies struggle against technological obsolescence
#140I have a team of 14 engineers in Pakistan. It wasn't always easy to do this and now I always feel at odds with hiring where everyone else is hiring or paying a premium for a western passport developer when I know I can get killer talent elsewhere. I feel the talent we have now has the ability to crush, kill, and destroy the talent in Silicon Valley "engineers" at a fraction of the price in terms of output to input ra…
The vast majority of comments here are from people with first hand experience of the level of incompetence from large I find consultancies. I have personally witnessed a major Indian IT consultancy cause problems with a file server migration. They had no idea that you needed to propagate permissions from the base folder. This took out production for 8 hours.
In the end, an on-site employee took over and fixed the issue in 5 minutes. It was pathetic to watch.
One day there will be a reckoning for these large consultancies. On that day, virtually no onsite IT employee will be unhappy.