just adding that.. most indian programmer that worth it would, like you, move out to earn the big bucks in USA,UK etc..
The problem are the one that stay in the coding factory because they won't cut it that get the well deserved reputation, and company still outsource their crap there.
Not many doctor's job description specify 'must have 5 years in.NET transplantation surgery method'..and refuse doctor with 'only' 1 year in.net combined with 4 times 5 years in other surgery technics..
So what, the manufacturer reimburse the customer , while pocketing the revenue from the thousand and thousand other people that went flawless..
Cost of doing business.
Know Lemon's law ?
So what, the customer have a faulty bit, manufacturer reimburse that customer, it's not like everybody have the same 'flaky bit'.
Now, if hundred of people have similar issue, chance that everyone of them have the same flaky bit is unlikely. Even let say that particular video card have a design issue(or driver or api etc), then more people would get problems. then the game manufacturer do some investigation and check why their software doesn't work where thousand of other do.. and find a fix.
Myself, I generally use only tested and proven techniques and call. I don't try to be clever nor use the latest API extension (DirectX 2012 FTW).
specially when the basics works just as well. I even try to be as generic as possible, and limit my use of the platform specifics. In case I need to port to other platforms. and that make it quite stable, even more, the next programmer that do maintenance on my code doesn't have to know every tricks and obscure call to understand what happening, more gain there!
4 - A robot may not masturbate, except where such action would conflict with the Second Law.
Pfft.. that actually the first law that already broken !
just adding that.. most indian programmer that worth it would, like you, move out to earn the big bucks in USA,UK etc.. The problem are the one that stay in the coding factory because they won't cut it that get the well deserved reputation, and company still outsource their crap there.
Not many doctor's job description specify 'must have 5 years in .NET transplantation surgery method' ..and refuse doctor with 'only' 1 year in .net combined with 4 times 5 years in other surgery technics..
FOX News : Obama's healthcare: Rationing of long care for cancer patient! Oncologist jobless!
So what, the manufacturer reimburse the customer , while pocketing the revenue from the thousand and thousand other people that went flawless.. Cost of doing business. Know Lemon's law ?
So what, the customer have a faulty bit, manufacturer reimburse that customer, it's not like everybody have the same 'flaky bit'. Now, if hundred of people have similar issue, chance that everyone of them have the same flaky bit is unlikely. Even let say that particular video card have a design issue(or driver or api etc), then more people would get problems. then the game manufacturer do some investigation and check why their software doesn't work where thousand of other do.. and find a fix. Myself, I generally use only tested and proven techniques and call. I don't try to be clever nor use the latest API extension (DirectX 2012 FTW). specially when the basics works just as well. I even try to be as generic as possible, and limit my use of the platform specifics. In case I need to port to other platforms. and that make it quite stable, even more, the next programmer that do maintenance on my code doesn't have to know every tricks and obscure call to understand what happening, more gain there!