Comment

Comment by throwawaydev123

> Do you have any trace of this in writing? Yes. One problem was they were merging their code without PR approvals, which caused many regressions. This is generally not allowed in our codebase. My manager was aware of it and the extra work it brought on to the team. It took months for them to correct this behavior, where as most devs, even interns correct in < week. And it only ended when I escalated the issue to my manager's manager. My manager's point though was that the coworker was "improving" which was... true. They had been submitting a higher percentage of PRs over the few months.

sorry for the vent... This was probably the most "solid" issue I had that wasn't subjective.

> Make sure it will not become a he said she said issue. Every interaction in writing. Good point, I should document our interactions even during meetings. I rely mostly on our written communications to think through our interactions but recollections of meetings are unclear. especially when I didn't view some interaction as memorable from my point of view at all but then later it's used as a vague example as "created fear" in a meeting.

> When doing things in writing, do not exclude th possibility of reading what you wrote and thinking "Holy cow, I'm the asshole". Either way, verba volant, scripta manent.

Also good advice. I am not by any means perfect in my communications and sometimes I really was the asshole in some situations.

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton