Big Ruby 2014

Cómo lidiar con los programadores para crear equipos de trabajo efectivos

Adam Keys  · 


Extracto de la transcripción automática del vídeo realizada por YouTube.

alright so first of all I have to thank you all for choosing to either wait the traffic out or not be in traffic here that is a cray mazing thing this slide is really just for Christmas he wanted me to play yes I'm doing so little alright so this talk

is called developers are from Mars developers are from Venus and that's a kind of a play on a self-help book that was available in the 90s when I worked in a Barnes & Noble the idea of the book was that it was the book was men are from Mars and then

a minute women are from Venus and the idea was that men and women men and women are very different think different etc so you can better understand your spouse or your girlfriend or whatever or your husband whatever your partner by understanding how they're

different and that might be a whole bunch of schlock but the underlying notion that we're all different and that there are ways we can think ways we can think about each other to better get along and work together I think is a really rad idea so this talk

is kind of my a journal of me diagnosing myself as a jerk and troubles trying to troubleshoot that code out of my manner I had realized several years ago that a lot of the problems I was facing as a developer were social problems and not technical problems

they were working with some people and some developers just wasn't very easy or possible for me because of personality conflicts or disagreements or whatever and I made it I was lucky for the first several years of my career to work with people who had

the sympathy or empathy to know how to work with me as a wily young upstart but eventually that's not going to carry you carry me through my whole career so I'd real i realize i had to level up my people skills but the tricky part is there's no

read me for people and there's certainly no manual page so all of this i had to i felt i feel like i had to reverse engineer it myself luckily there's a lot of books in non schlocky self-help stuff out there and i've tried to collect the things

I figure it out as I go I blog about it a bit I tweet about it and Here I am presenting about it so as I grew into a elder age developer a very elder as you can see I reached a point where I you know I said I was limited by who I could interact with in the

kinds of situations I could successfully negotiate so I felt I figured out basically I could accomplish very little on my own so I better get this teamwork and understanding people's stuff together or else how's this gonna be stuck in the corner doing

uninteresting things so once upon a time I realized that everyone is different not everyone is like me for better for worse and so I have to figure out how like you know when I meet someone or what I'm interacting with someone working with someone I figure

out what's what's going on in their head and how can I better communicate with and engage with that thing so I started debugging myself and reverse engineering those I work with because I can see what's going on in my head but I don't know

what's going on their head so it's a black black box situation and I tried to learn how to work with teams and communities that I'm a part of because every team and community is a little different just like every person is a little different so

the headline things here are to know people in general know yourself and know how what your tendencies are and practice empathy so the way I want to get start with this is no knowing people I like to well we all like to put things into their places put things

into their buckets or their pigeon holes or whatever and so I have developed some characters some personality types of developers and this helps me get a rough feeling of what what is motivating what is important to someone I might be working with in a team

or a community these are not after these are absolutely not science these are just my observations one or more of these a few caricatures maybe you and one or more of them may be on your team or people you see it really group meetings conferences on the internet

etc so the really the useful thing here is to recognize each character character type and then how how can I work most effectively with that character type so the first character type that I ever realized like oh this person is different from me with we're

grinders grinders are people who just hack out a bunch of code really quick who get features done really snappy who are pushing to production rapidly iterating quickly their product and feature obsessed all they want to do is get new stuff out experiment with

it see if it works and they're very cutthroat in their methods for getting software in a production one grinder that I worked with a few jobs ago he would push you know every 30 seconds and sometimes it wouldn't even be syntactically valid Ruby he

would just type some stuff in be like yeah I think this works deploy it look on the server and be like oh this page blew up and now people on my Twitter are being like hey why is this thing not working and then he would make a fix and immediately deploy it

in that works fine because our deploy only took like 30 seconds and so and he didn't write any unit tests and so to me this this guy was terrifying just absolutely like how is this actually working but the answer is he was obsessed with getting that feedback

[ ... ]

Nota: se han omitido las otras 2.702 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.