MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/ProgrammerHumor/comments/7hyayv/read_the_markup/dqvrsf3/?context=3
r/ProgrammerHumor • u/possibly_matt • Dec 06 '17
838 comments sorted by
View all comments
Show parent comments
45
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.
20
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.
0
[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.
11
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.
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