Skip to main content
8 events
when toggle format what by license comment
Oct 19, 2012 at 12:50 comment added IDrinkandIKnowThings @pdr - That sounds like a problem for the developer that is self conscious of his code. It is not the ops problem and it is not the op's place to address the problem of the other developer just the code that he may have to fix.
Oct 18, 2012 at 20:55 comment added pdr Sure. But you know if it's all one developer. And that developer knows if it's all them. And that developer knows you know. What's the point in pretending otherwise? Note that I never suggested being aggressive, but if you fail to be assertive then you might as well be passive (which is a perfectly valid option, particularly for a junior).
Oct 18, 2012 at 20:37 comment added IDrinkandIKnowThings @PDR - you do not have examples of problems from any developers you have examples of problems existing in the work product. I am glad I do not work where ever you do.
Oct 18, 2012 at 19:14 comment added pdr That is only true if you have examples of problems from several developers. Had that been the issue described, I'd have agreed.
Oct 18, 2012 at 18:46 comment added pdr Passive-aggressive is not limited to going behind someone's back, although that is probably the most common manifestation. Passive-aggressive is essentially attacking someone while trying to appear like you're not.
Oct 18, 2012 at 18:33 comment added pdr Yeah, ok, I see your point. Seems like a passive-aggressive solution though. Personally, I like to be shown how I can do things better. I'd rather someone be upfront about it than call a meeting and point to all my code and say "ok team, how are we going to fix this mess?"
Oct 18, 2012 at 18:26 comment added pdr "There is no need for you to point the finger and dress down the senior." Dress down, no. But part of addressing an issue is stopping it from getting worse.
Oct 18, 2012 at 18:23 history answered IDrinkandIKnowThings CC BY-SA 3.0