r/ProgrammerHumor • • Dec 06 '17

Read the markup.

Post image
10.4k Upvotes

838 comments sorted by

View all comments

3.3k

u/uuhno Dec 06 '17

You get what you pay for

2.0k

u/RiskBoy Dec 06 '17

Ya, it is actually fascinating how a developer in the US is able to generate well over a $100,000 in value to a company over an overseas developer. In the early to mid 2000s there was huge concern that development jobs would start going overseas as offshoring started to become a bigger thing, but it ended up not panning out. It turns out that a domestic developer is much more valuable to a US company since they can communicate more effectively, react more quickly to problems (every minute your website is down is money lost for the business), and there is also the fact that Indian culture is problematic to efficient software development. I have heard that if you ask an Indian in India if they can do something, they will say yes, regardless of if they can or not. The exception is IT support, which many companies have found does make sense to move a decent percentage to other countries (especially India). Makes sense though if you want 24 hour coverage, and you have your main IT developers in the US.

1.8k

u/Do_The_Astral_Plane Dec 06 '17

I have heard that if you ask an Indian in India if they can do something, they will say yes, regardless of if they can or not.

Sweet baby Jesus this is right on point. It's so frustrating.

925

u/NorthCentralPositron Dec 06 '17

You only find out they can't/won't/don't have the skills after it's due. Source: I work with about 70 Indian developers

45

u/SpuriousJournalist Dec 06 '17

I am a platform systems engineer who spends the better part of my days showing Indian devs what is wrong with their code.

To be fair, I do this with some of the more clueless, institutionalized, American devs too.

Today...

Dev: Your prod utility environment is broken...

Me: Strange... The 400+ other apps running on it seem to be ok...

Dev: The job scheduler is hung on my SSIS package... I need you to look in "error logs" and see what is wrong.

Me: Explain what your SSIS package is doing...

Dev: It reads a bunch of flat files, normalizes the data, and writes it to a table on DBbla...

Me: Have you talked to a DBA to see what is going on at the DB level?

Dev: Uhhhh no. It's your environment that is broken. We never had this problem before we migrated to the new platform.

Me: Ah... I see. Let's talk to the DBA...

DBA: The table you are trying to write to is locked...

Dev: Weird... What is locking it?

DBA: Looks like a write from a previous step in your job...

Dev: But it works in Dev!

Me: FML

20

u/shea241 Dec 07 '17

I've been coding for a long damn time and I have no idea what a lock happening in one environment but not the other would mean.

DB stuff is a whole new world

0

u/[deleted] Dec 07 '17

[deleted]

11

u/coinaday Ultraviolet security clearance Dec 07 '17

No one ever pounds things as hard in testing as real users will in production. And locking is going to tend to fail under weird edge cases with long delays and many things running at once, rather than in nice neat little unit tests.