I work with Nadya, and I can say that all of us fear her going into our code and changing it just because she feels she can make it better. Nadya has a tendency to take over other people's work and make it her own, without permission. She has been talked to on more than one occassion by our manager not to do this, but she doesn't listen. The m.s are a minor annoyance to all of us. She will take a working piece of code in production and replace all the variables with m.s. She also implements "improvements" that have caused serious problems in the past.

I respect Nadya's ability; she is a talented programmer, but she does not work well with others. If she had her way she'd take over the entire project, and my manger knows this and has told us all to stand up to her when necessary.

>My underlying concern was not whether or not the code should be changed whenever it can be done without going against standards, guidelines, or breaking other code, but rather how she went about it. She is already trying to resolve a touchy situation at work and this only compounds it. It is obvious that her coworkers are resentful that everytime she touches something, she modifies it in order to optimize it, enhance it, or just for aestetic reasons. They have already left childish nasty grams inside her code (do not do this...) and they removed her changes. Before she proceeds she should clear it with her boss or risk more animosity among the developers. She is not working in a healthy atmosphere and this will only make it worse. Sometimes it is better to 'let things go' if they are not truly necessary in order to promote a better working environment - unless she is willing to go to work for herself. Naomi knows that her changes made the code more efficient - she knows
>she was right - but it is not always better in the long run to be 'right.'
>