The Monster on the Project
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
Title |
| |
Title of Series | ||
Part Number | 16 | |
Number of Parts | 48 | |
Author | ||
Contributors | ||
License | CC Attribution - ShareAlike 3.0 Unported: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this | |
Identifiers | 10.5446/33217 (DOI) | |
Publisher | ||
Release Date | ||
Language |
Content Metadata
Subject Area | ||
Genre | ||
Abstract |
|
DjangoCon US 201716 / 48
2
5
6
14
16
23
26
30
31
32
34
39
43
48
00:00
Monster groupFood energyMonster groupLevel (video gaming)Computer animationLecture/Conference
00:42
Multiplication signProcess (computing)Open sourceDemo (music)NeuroinformatikHacker (term)Information securityResultantSound effectMonster groupSoftwareGradientBus (computing)Division (mathematics)Level (video gaming)BitStress (mechanics)Uniformer RaumObservational studyOcean currentComputer animation
03:05
Video gameComputer animation
03:37
Group actionAddress spaceSoftware testingDean numberObservational studyForm (programming)Stress (mechanics)VotingIntegrated development environmentEntropie <Informationstheorie>Core dumpConnectivity (graph theory)Open sourceInsertion lossArithmetic meanData managementCASE <Informatik>Cycle (graph theory)1 (number)PhysicalismFlagProcess (computing)Error messageMathematicsFormal languageResultantMoment (mathematics)Multiplication signSound effectBoss CorporationSystem administratorWater vaporDecision theoryOverhead (computing)Rule of inferenceStatisticsFreewareEscape characterFrequencyOcean currentWave packetDrawing
10:33
Integrated development environmentState of matterCASE <Informatik>Data managementRule of inferenceLevel (video gaming)Event horizonMultiplication signProcess (computing)Natural numberBitHierarchyForm (programming)CodeMereologyConvex setExterior algebraVideo gameObservational studyGroup actionPerspective (visual)Incidence algebraStandard deviationShared memoryAbstractionExpected valueLattice (order)Row (database)Boss CorporationPoint (geometry)Dependent and independent variablesAttribute grammarComputer configurationDecision theoryCharacteristic polynomialStress (mechanics)Archaeological field surveyExtreme programmingDifferent (Kate Ryan album)Sign (mathematics)CausalitySoftwareSet (mathematics)Online helpModal logic2 (number)Computer animation
16:47
Revision controlCodeRevision controlTelecommunicationCodeGoodness of fitInheritance (object-oriented programming)Image resolutionData managementIntegrated development environmentGroup action1 (number)Office suiteBasis <Mathematik>FrictionMoment (mathematics)Computer-assisted translationOpen sourceNegative numberExpected valueSelf-organizationSet (mathematics)Thermal conductivityMultiplication signSoftware frameworkAlgebraic closureOnline helpProcess (computing)RootContext awarenessInformationControl flowData conversionLine (geometry)Maxima and minimaQuicksortRule of inferenceType theoryCompass (drafting)BitStatement (computer science)Error messageArithmetic meanWebsiteObservational studyComputer animation
23:01
Group actionPoint (geometry)MereologyMultiplication signParameter (computer programming)Stress (mechanics)Image resolutionArithmetic meanType theoryVariable (mathematics)Computer-assisted translationDeterminantData structureQuicksortIncidence algebraOrder (biology)Revision controlModal logicData managementFamilyLecture/Conference
26:39
Coma BerenicesReading (process)JSONXML
Transcript: English(auto-generated)
00:15
It's the last talk of the day, let's try and keep that energy up, stay awake, we've got
00:20
a picnic coming, stay on top of that. So as my lovely host, Sasha, introduced me, I am Tibbs, we're here to talk about monsters and projects, and if you're not here to talk about that you're probably in the wrong place, so you might want to try next door. And if my clicker will work, we can get started. So I'm Tibbs, and this is how I imagine myself when I'm on stage to try
00:49
and avoid any nerves and stress and fear about all of you out there. So if you would also like to imagine me as a little DomoCon monster up here, I'm more
01:01
than happy to play into that. Currently I work at Intel, well I work with Intel doing security assessments of the open source software that they want to use in-house and the software that they create that they want to push out to the open source community, and that's based out in Hillsborough. I am
01:21
originally from Scotland, so you might hear a little bit of that accent come through, just kind of smile. At 24 I left a career to attend uni for the first time to study computer security, forensics, and ethical hacking, and the career that I left was actually in HR, and I had no idea at the time that I
01:43
would use the skills and knowledge that I picked up in HR more often in my current job and in the open source community than I ever did when I was doing HR full-time, but that's how it is. So it helps if you turn it on. So
02:08
before I moved into tech and before I went into HR, before I had any inkling at all that I would not grow up to train dolphins to speak English, I was this
02:21
kid. This was me going to school pretty much every day from about seven years old until graduation. I hated school, not because I didn't like learning. I love learning. I love, I learn new things every day and it's great. I hated school because I was really badly bullied and as a result I had poor grades, I had poor
02:42
attendance because I was always sick, and I was a really sad, lonely child and I don't remember how to do, I don't remember learning how to do long division and maybe that's why I'm not very good at it, but I do remember in vivid detail the first day the other kids started throwing rocks at me from
03:02
the bus. When I wasn't reading every fantasy and sci-fi novel I could find, I spent my youth dreaming about being an adult and escaping my unhappiness at
03:23
school. I thought when I grew up I wouldn't have to deal with bullies. I could leave all of that at graduation, get my diploma and go on to bigger and better things. I could actually start my life and that worked, kind of, until I
03:40
was 23 and I started a new job doing insurance repair administration. I mean wasn't the most exciting of things, but my boss must have sensed blood in the water because it didn't take long for him to start picking on me. When what started as small complaints about my work, making up rules that didn't
04:03
exist for everybody else, soon escalated to him isolating me in the conference room and berating me until I broke down on tears. It was horrible. I may have been an adult, but I felt like I was eight all over again. I was back
04:21
in school and somehow I still lacked the knowledge and skills to deal with this bully. I knew what he was doing was wrong, but I couldn't find my voice to speak up. I felt trapped. This is really not uncommon at all. In fact, toxic
04:42
behavior is a known problem in the workplace and has been for a while. Unfortunately, statistics show that that problem is only growing. Now, while current studies are focused on workplace and educational environments, as a result a lot of the language that I'm going to use here is going to be focused on
05:01
these environments. However, toxic behavior is a concern and can present in any environment where people cohabitate or collaborate. I mean, would any of you be surprised to know that I've heard stories about toxic behavior in free and open source environments, projects? Yeah. So when I
05:26
was in HR and investigating complaints, I would hear from managers and project leads all the time. They'd say over and over again, they'd say, so what, we have a couple of difficult people on the project. They're the high performers. They're the rock stars. They're the ones who get things done. Well, studies
05:44
show that no matter how well a toxic personality performs, their behavior drags down the performance of the team to below what it would have been without them. They actually negate any performance boost that management or
06:00
anybody else may think that they provide the team. But why is that? Well, being bullied, as was the case when I was a child, induces stress, anxiety, depression, and a host of other physical and psychological medical issues for those who are the target. And new studies show that it can
06:22
even create a form of post-traumatic stress disorder like that seen amongst soldiers returning from war. More concerning, though, is a study showing that the stress of bullying may actually lead to bad decision-making. In 2009, a study found that stressed out rats fail to adapt
06:43
to changes in their environment. A portion of their brain actually shrunk compared to the same region in relaxed rats. Let's think about that for a moment. Their brain actually changed as a result of the stress that they were
07:01
experiencing. And these findings suggest that stress may actually rewire the brain and create an inability to make good decisions. And maybe this is why we see in people who are abused by their partners that they return to them over and over again before escaping the cycle of abuse. Now, it's not
07:25
easy to speak up when a person is being targeted by toxic behavior. And abuse can have horrible effects on self-esteem. And often it starts so mildly that we convince ourselves that we're imagining it. But even when we do
07:42
speak up, we're often met with disbelief, or victim-blaming, or gaslighting, or because we're the ones speaking up, we're treated as the person who's the problem. Sometimes we're even fired for it. The worst cases are when people take
08:02
their lives because they see no other escape. And that happens more often than you'd think. That's for people who stay in hostile environments. I mean, it took me a while to understand what was happening to me when I was being
08:21
bullied in that first workplace situation. But ever since, I've been very willing to leave companies and projects at the first red flag that this might happen again. And turnovers for teams with toxic personalities are higher than in those teams without it. High turnover is a problem both for business
08:45
and for FOSS projects. For companies, it's expensive. There's a lot of expense and man-hours lost in recruiting, interviewing, and training new employees. On top of that, new employees typically have a four to six month spin-up
09:03
period before they're actually able to perform at full productivity. Outside of this, there's reputation costs and the hit to morale of the remaining team members. I actually once worked at a company that had a betting pool on how long new employees were going to last. It wasn't a very welcoming environment.
09:25
And you can bet that as soon as I found that out, I put my resume back on market. I was looking for a new job because I didn't want to be there. The toxic environment had become such a core component of the work culture that they were unable to see that it was actively sabotaging their efforts to improve.
09:45
FOSS projects can also suffer from reputation loss as well as potentially losing new and existing contributors. FOSS projects risk losing the undocumented tribal knowledge that members take with them when they leave.
10:00
I think we all know companies and projects that we wouldn't even consider working with. I mean, we still have Uber dealing with a fallout of the last half a year or more, and Google has certainly taken a reputation hit in the last couple of weeks. So we know the consequences. But what exactly is the problem?
10:25
What is toxic behavior? And how do we recognize it when we know we have a problem? Well, for employees and contributors, there are lots of forms of bullying and abuse. And it'd be really difficult for me to cover them all here.
10:44
But in a survey that was carried out recently, the most common reported signs of bullying included being falsely accused of mistakes that they didn't make, their comments being ignored, dismissed, or not acknowledged, having a different set of standards or policies applied to them that aren't
11:02
applied to anybody else, gossip being spread about them, or not being stopped by their manager, being constantly criticized by their boss or co-worker, belittling comments that were made about their work during meetings in front of other people, being yelled at by their manager in front of other people,
11:24
perhaps they're purposely excluded from projects or meetings, or credit for their work has been stolen. Lastly, they were picked on for personal attributes. These are all things that, for the most part, are against code of conduct,
11:42
but can sometimes be hard to pinpoint. So what about from an employer or project lead perspective? Well, my personal experience is that people who treat others downstream poorly or who hoard knowledge are potentially toxic personalities. Studies show that employees who are overconfident or
12:04
self-centered are more likely to have toxic personality traits. But what surprised me about the same study was that they found that people who believe that rules should always be followed were more likely to exhibit toxic behavior. The researchers hypothesized that this was due to the
12:23
subjects telling the interview what they thought they wanted to hear. And they said it could be the case that those who claim the rules should be followed in all cases are more Machiavellian in nature, purporting to embrace whatever rules, characteristics, or beliefs that they believe are more
12:42
likely to obtain them the job. And there is a strong evidence that Machiavellianism leads to deviant behavior. It's also important that the employer and project lead look at the behavior of the team members around a
13:00
potentially toxic person. Stress will often affect time management skills, ability to focus, health, and cause burnout. And if the behavior of an employee or project member alters suddenly, really the first step should be to talk to them proactively and see what's going on. Maybe they're not being
13:23
bullied. Maybe they just have something going on in their personal life. But talking to you, talking to them about it will help you know what's going on and will help them because sharing is always a good way to help relieve a little bit of stress. But the kind of second step there is if you ask
13:45
somebody what's going on for them, how they're doing, you really need to actually listen to them. It doesn't do any good to ask and not absorb that. I think that a lot of us have experienced the feeling of talking to somebody without actually feeling heard. So now that we've identified the problem,
14:05
how do we fix it? For employees and contributors, it can be really difficult, but the best course of action is to stay professional, don't reciprocate, disengage where possible, journal the incidents. Like seriously,
14:23
just get a piece of paper and start writing things down. It'll keep things straight in your mind and give you a record so that you can refer to it later on. And I know that for me, it really helps when I feel like the person that I'm dealing with has an alternate experience of events,
14:43
as sometimes happens, especially with gaslighting, which is the process of somebody telling you that something you experienced didn't happen the way that you experienced it. Talk to your manager or to the HR person if the bully is your manager. In FOSS situations, this can be a little bit more difficult because it's
15:04
not always that hierarchy in smaller projects. But talk to somebody else in the community and start kind of asking, seeing if other people are experiencing the same thing you are. If no action is taken, it may be time for you to look
15:23
for your next opportunity. But more importantly, talk to your friends and your family and start engaging on that network of support that you have and share your experiences. And if you have time and resources, if the bullying or toxic behavior is really affecting you badly, consider seeking therapy to help get you
15:44
through. In regards to the person who is exhibiting toxic behavior, it's sad but important to acknowledge that in extreme cases, expulsion for the group
16:01
is a step that may become necessary. People have to want to change and to be able to adapt to new expectations. And as much as we might want them to, and we might want to, we can't fix everybody. That said, I think that expulsion should really be like a last-ditch, no-options-left decision.
16:24
There's a lot that can be done to try and reform a person who is exhibiting toxic behavior. Now, you might ask what the point of that would be if they're bringing down the whole team. But in response to that, I'd like to say that assholes are
16:43
people too. And like all people, they deserve to be treated with dignity and compassion. And studies show that actually the reformation of an offender is more productive and less disruptive to the group. The project doesn't lose the tribal knowledge that that person has, and the injury parties will actually benefit from going through the
17:06
resolution process and getting closure rather than just having the issue go unaddressed because the person's now gone. It may not surprise you that adults are actually a lot like big children. I know I am. A lot of the tactics that a manager or project lead can
17:28
employ to tame toxic behavior are ones that we learn from parenting books. And the end goal is finding a new way to motivate the worker. Now, kind of at the very base of things,
17:40
there are two ways of doing this, the carrot and the stick, offering a reward for good behavior and a negative action for poor behavior. The trick is learning which rewards and punishments will motivate which workers. And this is going to be different for everybody, so there's a little bit of trial and error involved. It's also important throughout the process to be incredibly clear about which behaviors are unacceptable and that they must
18:05
stop immediately. I have seen time and time again when I was in HR people who would be brought in and told that their behavior was unacceptable, listened to the letter of the rule of the law, and did the bare minimum, they totally would rules lawyer exactly what they
18:27
could and could not do, and would actually kind of try and skirt that line just to spite the person that was enforcing the rules or sometimes the person that reported them. So it can be really important to watch out for that type of behavior. Reformation does take
18:45
work from everybody involved, the organization, the person, and the team, but it can also be really, really rewarding. To that, an ounce of prevention is worth a pound of cure. Setting
19:02
behavior expectations right from the beginning with a code of conduct or a set of project values is going to stop bad behavior before it starts, or at least provide an expectation and around that a robust framework needs to be put in place to support members when they
19:23
feel that they've experienced bullying. Fostering good communication skills and providing a safe environment for people to talk about feelings and conflict resolution is also really vital. Look at the learning and communication styles as a team because we all communicate
19:44
differently and we all learn differently, and sometimes these mismatches can cause friction and learning how to deal with that and how to communicate through that is a good way of stopping conflict before it happens. Teach conflict resolution skills and use
20:04
statements like, when you say blank, I hear blank. Is that what you meant? It can be really a good way to remove the feeling of being personally attacked and stop somebody from feeling the
20:22
need to get defensive about something they've said or of action that they've done. Also, don't penalize people for needing to take a break from difficult conversations. People get overwhelmed and everybody in the office or on the project should be able to say, I need five minutes or I need overnight to think about this. Let's come back to this
20:44
conversation tomorrow. It doesn't mean that the issue is resolved or that we're not going to talk about it anymore, but people do often need to take time away. I'm definitely this kind of person where when I'm in a confrontation, often it'll get too emotional for me and I need to
21:02
take time away to sort through what's going on in my brain and what I'm experiencing versus what's happening. In the wider community, we need to value soft skills, not just coding abilities. All these things I'm talking about like conflict resolution, communication, these
21:22
are all soft skills that take time to develop. When we brush bad behavior under the rug, just because somebody is a really great coder, we're doing a disservice to everyone, including that person, because we're denying them the chance to grow and improve as a person. More
21:40
than that, we as a community need to talk about this problem and call out poor behavior when we see it. We're getting there, but there's still a lot of room to grow. Our communities also need to make an active effort to discuss mental health. Often mental health issues are actually the root of toxic behavior, especially unaddressed mental health
22:05
issues. If mental health was not such a taboo topic, people would feel more free to talk about the problems that they're experiencing and seek help. I'm actually an advocate of the Open Sourcing Mental Health charity, which seeks to raise awareness and actually
22:20
educate people about mental health issues within the open source community. They provide resources to companies, projects, and people who are struggling with mental health issues. The website is really incredibly helpful and full of a lot of really great information, so I would highly recommend that you go have a look. These are some further resources.
22:49
I'd like to take a moment to thank DjangoCon for having me, and I'd like to thank everybody here for being so quiet and attentive. You've been a fantastic audience. Does anybody
23:02
like this cat have questions? On a personal note, confronting abusers can be a scary thing for the person about to do the confrontation. Definitely, yeah.
23:20
Do you have any tips on how to deal with that sort of thing to get yourself to a point where you can confront? I think that talking to others and taking somebody with you can be really valuable. In HR, I say we. In British HR, when we're having a disciplinary action or even some
23:43
kind of serious talk with an employee and an employer, a manager, we always encourage the employee to bring somebody with them. Just somebody there to be a witness, because then if something happens, if somebody says something inappropriate, then you've got somebody there who also heard it, and it is less of a he-said-she-said kind of situation.
24:06
Also, it can be really good for the person who's making the complaint to be able to have that extra person there just to know that they're not alone. I know that that gets me every time, feeling like I'm alone in something.
24:20
Having somebody there with you, or even sometimes I've seen people write down their concerns, and having that piece of paper in front of you ... I'm guilty of this all the time. My brain goes blank. Having a piece of paper that has all the points that I wanted to make in front of me can be really, really helpful.
24:41
Know that the fear and the stress is temporary, and that once you get that all out there and start that conflict resolution situation, things will get better. It may not end the way that you want it to, but at least that feeling of being in limbo will be over.
25:03
You mentioned that sometimes it's necessary to remove someone from the group. Do you have any parameters you can use to say, this person has been given the opportunity to change, but it's time to remove them because ...
25:23
I think that there are a lot of variables. A lot of it depends on what type of behavior the person is exhibiting. A lot of it depends on how sincerely they're trying to improve. A lot of it also is up to the group and how much stress and conflict that the group
25:51
can actually itself handle. I've certainly seen situations where we've had somebody who was really great, but we just at that time didn't have the structure or the support
26:04
necessary in order to include them as part of the group. That didn't mean that they wouldn't be welcome in the future when we did have those resources available, but sometimes it is just a determination of what resources are available and how willing the person is to really try and improve.
26:21
If you have a specific incident that you'd like to talk about, I'm happy to discuss that with you later. That's about all the time we have for questions. Thank you very much again, Tips. Thank you.