5 ms·
I'm not sure if I understand some of these: "It was near the end of the working day, around 5pm, as the person coordinating the developer recruitment in our ar
by repomies691 11y ago
I'm not sure if I understand some of these:
"It was near the end of the working day, around 5pm, as the person coordinating the developer recruitment in our area I ping’ed our Slack channel to encourage our developers to start reviewing some code tests from job candidates. One person replied: “My end of day activity is doing the stuff I should have been doing all day instead of the other things that came up.”"
What was the treated poorly part? Someone priorized some other work over his assignment, or something? I personally think overtime should be avoided, but often people do it voluntarily.
"A senior software architect who I used to respect walked close by in a meetup. We worked for the same company a while back so I smiled, said hi and was about to start a conversation, he quickly cut me off with “I need to get a drink” without looking at me and wondered off."
Seriously? Everyone has a bad day now and then. This is of course not nice behaviour, but I wouldn't consider it worth remembering or mentioning as "being treated poorly".
"The general manager who is non-technical, asked me to investigate options to uplift our ageing bespoke ecommerce solution. Upon delivering my findings, I was told that “your findings are biased.”"
What would be the proper way to communicate this? If the manager thinks that the findings are biased, would it be better not to say that, or communicate it in some other way?
- fredwu 11y agoHi, Author here, I can see why you have these questions. I tried to keep the moments short so left out some details. For the first one, it was the passive aggressive tone and the fact that it was posted in a public channel. This person in one other occasion, stormed out of a meeting room whilst another colleague was trying to explain something. For the second one, later on through mutual colleagues I realised that he essentially thought very little of me because at the time I was a junior developer so I made lots of mistakes in my code base. In my defence though, I was on my own and I had to learn Rails myself. For the third one, I put the "non-technical" part in to indicate that my manager does not have the technical capability to determine whether my findings were biased. It was more so that he had his agenda and just wanted me to confirm his approach from the technical perspective. Hope that clears things up a little bit. :)
- ownagefool 11y agoThese stories kinda make it sound like you keep getting reprimanded for shelling into servers and installing random packages. If you aren't somehow resonsible, keep your chin up, not everywheres filled with those kinds of people.
- repomies691 11y agoTo be honest I think you should give people a little slack and relax. You are taking things too personally. Everyone has a bad day now and then. Based on your descriptions to me it looks like "not treating people poorly" would require almost superhuman capabilities from managers and coworkers. They probably have also lot of other stuff to worry about as well.
- deleted 11y ago[deleted]
- fredwu 11y agoI think I do, hence I put this sentence in the article: "There are a few of these moments that I still find hard to swallow, but most of them I simply chuckle whenever I think about them. ;)" For most of these moments, it was more a reflection of my personality if anything - under the same circumstances, I know I _wouldn't_ treat others the same way I was treated back then. I much prefer to use softer tones and more positive ways to start those conversations.
- repomies691 11y ago"under the same circumstances, I know I _wouldn't_ treat others the same way I was treated back then" I wouldn't dare to make that claim. Every situation is different and also everyone's mood varies from day to day. It is very difficult to be that nice guy all the time.
- bakeryOnMain 11y agoIt should not be difficult to be a nice person all the time. We are building software, and/or managing a product/team. It's a communal effort that requires empathy, kindness, and love. If you are one of the few who can't love your fellow coworker/subordinate/boss then you are toxic. Unfortunately, bullies existed on the playground and they exist in the software industry too.
- staticelf 11y agoEspecially the last one I find interesting, I have the perspective that if someone did dismiss me and didn't say anything or gave me a clearly bullshit reason I'd find that much more offensive than telling the truth to my face. Maybe the person wasn't biased, but obviously the manager thought so.
- awinder 11y agoThe "you're biased" line is a dismissive remark in a sense though. Everyone's biased, to certain extents, and keeping bias out of research is really tough sometimes. But: 1. A lot of times, this statement is used as a weak crutch by someone who had a different idea, but can't properly explain their side of the position and work towards why there was a difference in conclusion. Usually it's because the person that said "you're biased" is actually carrying a ton of bias into their viewpoints. 2. Even if someone was biased, do you think telling them that they're biased is going to bring resolution? Of course not. See point #1.
- pc86 11y agoThe correct response to being accused of bias is to step back, review your finding, your possible biases, and either adjust your findings or have an argument for why you don't feel they are biased. Not to pout and say you're being treated poorly.
- awinder 11y agoI don't know what the guy did in the moment, but you're right about how you should react in that moment. That said, bitching about bad managers is a time honored tradition as old as management itself, so I don't really see the big deal with blogging about it.
- repomies691 11y agoI would prefer if someone said "I think you're biased" instead of being lied to with some bullshit excuses to dismiss my point/research/whatever.
- awinder 11y agoThe "investigate options" one was one of the few situations that I could see a possible slight. I've seen managers who play this dumb game where they put people on a research problem, and the job isn't for the engineer to do unbiased research & prototyping, but it's instead to reinforce whatever argument they were originally pushing for (but your "job" is to actually bring facts in). I've heard the "you're biased" line enough from those kinds of people to just shrug it off and move on, but I've also seen engineers who become paralyzed trying to figure out "what the boss really wants". For my biased point of view, these managers fit into a category called "the worst" anyways, so getting worked up about it is probably not worth it. As an aside on the not understanding front, what was the deal with the team lead scenario? In my experience team leads aren't managerial positions so I don't quite understand why the guy was so concerned with other employees salaries. There was also a lot of missing details there, the author could have been making significantly more, and so the raises were treated differently? That was definitely a peculiar one.
- exelius 11y agoYeah, generally at any company large enough to have a dedicated HR function, dev leads usually don't get informed or consulted in salary decisions. I was confused by that one too; his expectations were out of line on that one IMO. The reason for this is that it's not at all uncommon for dev team members to make more than team leads if they have a specific skill set that the market values more.
- fredwu 11y agoHi, Author here. Unfortunately that one was from a small startup where I was responsible for evaluating my team members' performance and salary.
- exelius 11y agoYeah; unfortunately at startups where roles / expectations aren't clearly defined, this type of stuff happens. Honestly I doubt it was out of malice; it's simply easier at a small company for the CEO to make all the comp decisions themselves than have to consult half the company about information that's supposed to be confidential. He may have thought he was doing the right thing to do -- startup CEOs are usually just winging it.
- gmantom 11y agoMost are ok but the one on code review for new candidates and slack that one is off. Getting offended because people have stuff to do dosent mean you're being treated poorly.
- protomyth 11y ago> "It was near the end of the working day, around 5pm, as the person coordinating the developer recruitment in our area I ping’ed our Slack channel to encourage our developers to start reviewing some code tests from job candidates. One person replied: “My end of day activity is doing the stuff I should have been doing all day instead of the other things that came up.”" The developer is being treated poorly and gave a response to indicate why s/he was being treated poorly. I don't see the problem other than the person coordinating developer recruitment should respect people's time more. > "A senior software architect who I used to respect walked close by in a meetup. We worked for the same company a while back so I smiled, said hi and was about to start a conversation, he quickly cut me off with “I need to get a drink” without looking at me and wondered off." If I knew the person well enough, that one is actually a "I need to talk away from here" or a warning to not talk here. I've had friends go with that, but it really is not clear from the context what is going on or has gone on.
- jimbokun 11y ago"If the manager thinks that the findings are biased, would it be better not to say that, or communicate it in some other way?" Describe the points of the analysis that seem biased, without even using the word "biased". "Looks like you only considered..." "I don't see any mention of..." "But you didn't mention [superior feature] of [other product]." "Biased" is an accusation against the presenter, as opposed to asking questions or making comments about the analysis directly. Making a personal attack does not help in making a good decision.