Arthur (or Art, take your pick) has been a software engineer for 20 years and has worked on things as exciting as analysis software for casinos and things as boring as banking websites. He is an advocate for talking openly about mental health and psychology in the technical world, and he spends a lot of time thinking about how we program and why we program, and about the tools, structures, cultures, and mental processes that help and hinder us from our ultimate goal of writing amazing things. His hair is brown and his thorax is a shiny blue color.
Conflict at work is as inevitable as the tides - like the old joke says, if you put five software engineers in a room, you’ll have seven opinions. Whether the conflict is over what language to use, what frameworks are the new hotness, or even just tabs vs spaces, conflict can get ugly. Tempers flare, positions are staked out in absolute terms, feelings are hurt, working relationships are destroyed… if only there were a way to avoid the negative consequences.
What if I told you that there is? Let’s take a journey together towards a wholly different approach to conflict - a collaborative one. In this talk, you’ll learn how to use conflict to fuel better software, better teams, and better companies. You’ll learn how to structure your team’s environment to draw out good conflict, to squelch the bad conflict, and to handle conflict when it becomes personal. We’ll discuss how to manage different confrontational styles, avoid self-sealing prophecies, and even how to deal with conflict when you lack control. Come get a jump start on your next argument!
Searching for speaker images...