3 ms·
I usually find this sort of reply distasteful, but it seems appropriate in this context... I don’t know if I can’t send you the code, I’ll have to ask my emplo
by tjr 14y ago
I usually find this sort of reply distasteful, but it seems appropriate in this context...
I don’t know if I can’t send you the code, I’ll have to ask my employer. (Which seems really silly thing to do, considering you want to get the code to show it to some other company that you want to hire you).
The parenthetical phrase is not a complete sentence, and should have been placed before the period following "employer". "Which" should not have been capitalized. "seems really silly thing to do" is missing an article. The final period would be rendered redundant by proper placement of the parenthetical phrase.
Here is the deal, if you aren’t coding for fun ...
A colon after "deal" would be better.
driven by whatever the crazy professor think is a valid coding standard
"crazy professor" is a singular noun. Either use "thinks" or "crazy professors".
I can understand crazy coding standards, what I can’t understand is why someone would submit something that would raise so many red flags so quickly as part of a job application process.
This sentence just doesn't flow well, but that aside, the comma should be replaced with a semicolon, or it should be broken into two sentences.
And I'm sure there are more errors.
But why do I care? If someone is going to write an angry rant about how a job candidate submitted code that used suboptimal coding standards, then it would be more convincing if the author would avoid writing this angry rant using suboptimal grammatical standards.
Thanks!
- eru 14y agoYou might try sending this to the author (e.g. as an email) for them to fix it.