3 ms·
Keep in mind, you might very well be facing somebody who feels the need to prove himself. If this is the case, then the issue is marginally technical; his need
by meunierc 17y ago
Keep in mind, you might very well be facing somebody who feels the need to prove himself. If this is the case, then the issue is marginally technical; his need to be right is his prime motivation.
Your first response was perfect IMO.
In situations like this you need to manage a person, not software nor a project. If he's in a sibling reporting branch, you may want to discuss the situation with your lead. He may decide to go ahead with the modification in the interest of good relations. If he does, you must understand this is not a judgment from your lead on the quality of your work.
- sunkencity 17y agoYeah I second that it might well be someone who wants to prove himself, or a geek with poor social skills who want to befriend you by commenting on your work. It is pretty rude to just ask outright of anyone to rewrite their code, a writing such a request as a suggestion or opening to discussion is much friendlier. It would not be rude if there's a critical problem, but just a small performance increase is way out of line. The correct way to deal with this is of course to add the script tags at the bottom of the page ;) (apart from your coworker not noticing - it's better for performance as (most?) browsers completely stop doing anything but loading javascript when they encounter a javascript tag).