Pair Programming: Better Than Adderall | Accessibility NYC Meetup Recap

Matt Kleiman

On December 4, 2018, Accessibility NYC hosted a meetup entitled “Pair Programming: Better Than Adderall.” Presenter Matt Kleiman, software engineer at Pivotal Labs, described how his Attention Deficit Disorder (ADD) and other learning disabilities deterred his success on traditional software development teams.  He shared how the process of pair programming provides him with a feedback loop for his thoughts and a partner to hold him accountable eight hours a day, providing him with a disciplined structure for operating and serving as the perfect counterweight to inevitable distractions.

Here are some of our highlights from Matt Kleiman’s presentation: 

Transcript: A11yNYC Dec 2018 - Pair Programming: Better Than Adderall: Matt Kleiman

great all right well hello everyone welcome to accessibility New York City the December 2018 edition very happy to have you all here at thoughtbot we host our meetup here monthly and we really appreciate thoughtbot being our event host my name is Thomas Logan I'm one of the co-organizers of the event we have two co-organizers not here tonight Sean laureate and Cameron Cundiff and we want to celebrate we have a fourth co-organizer male Tyson gach if you've been to our events he's been here pretty consistently over the years so we're happy to have him now part of the team helping organize the events so any of us if you haven't met us that you know come up and meet us if you're interested in presenting at the event or you have a topic you'd like the New York City

community and the YouTube streaming world to know about please let us know at the event we have our live captions communication access real-time is provided by a white coat captioning and thank you to diane our captioner tonight she's providing these captions remotely and we do this as part of every event that we do here for the Meetup I want to thank dolly McPhee from the Internet Society of New York who produces our live stream the accessibility special interest group the Internet Society of New York you know that's the best interest group in our opinion so thank you to jolly for always putting together like an amazing stream here we've got some cameras and speakers in the back so you know we strive every event to make sure that people that can attend in person can fully participate in the online stream and any

presentations you might have missed of our meetup which has been going for over three years now you can find those on youtube with the captions and you know with the accessible alternatives so we're very excited tonight to have Matthew Klieman from pivotal apps DC to speak with us pivotal labs was actually the first event host for accessibility New York City here in New York so I already have a great connection with that company and super excited for Matthew's talk tonight I think it's one of our most exciting titles maybe our most exciting title why pair programming is better than adderall and I'm excited to learn from you Matthew so take it away Thank You Thomas all right thanks everyone for joining and for everyone on the livestream I really appreciate the the audience and your attention as you said my name's

Matthew Klieman I'm a software engineer and manager in the DC office of pivotal labs but I started my pivotal career here in the New York office today I'm gonna tell you about my journey to my journey as a software engineer and my journey to finding pivotal labs and the practices of pair programming and test-driven development and how they've helped me the message that I'm trying to convey here is that I hope to like share that we should all seek out work environments that nourish our strengths as as humans and as as workers so I have ad D attention deficit disorder I also was diagnosed with some other learning disabilities when I was younger and a lot of it especially ad D centers around or it's in the category of like an executive functioning disorder although

I don't really like to use the word disorder but specifically executive functioning what that means is it's like the ability to to analyze and plan out tasks and make decisions about those tasks do them in a certain order to carry them out for myself as someone with a DD I'm capable fully capable of doing all the things that I just mentioned however I have a really hard time doing them in the order that most of us might expect the these tasks to be done in you know people with a DD are traditionally defined by their distracted nassif achill T focusing and I I think that these things are very much true about myself but I also like to define it as a gift you know the things that me as someone with a DD the gifts that I have from this are my

creativity my interpersonal intuition my ability to kind of like see other people in maybe in ways that most people don't don't see my exuberance as evidenced by me coming here and talking with you all today and my natural curiosity and as you'll see through the the journey of my life till today it's it's only more recently that I've kind of discovered how how these how these traits our gifts in my career so the journey starts let's say around fifth grade I my parents were both public school teachers and I was a very high functioning student I did very well in school and I got good grades and all that but my parents were I think partly because of their training as teachers were able to see that even though I was doing well on pay I was really struggling I was putting a

lot of energy a lot of effort into everything everything that I was doing and through their understanding of other students that they had with a DD they decided to have had me go through some testing some psychological testing and that's you know basically the first step in in you know in in diagnosing someone with a DD or some other learning disability to understand you know uh at a clinical level how someone might be differently abled and once that happened I was given that diagnosis I was given accommodations all through middle school and high school my teachers were giving sorry my teachers were giving me extra time on on tests so that I could spend a little bit extra time using coping skills that I was taught of like how to organize my thoughts onto paper teachers

would give me notes so because it was very hard for me to take notes as people were speaking another thing that we discovered through that testing was I had a difficulty with auditory processing the ability to understand what is being said to me if there's no visual cue as well and just like just to kind of wrap all that up I also before going to college had another series of tests to reaffirm that diagnosis it was pretty obvious to me my parents my teachers but in order to continue getting the same accommodations as afforded by you know the the government's like accessibility laws in college I had to get that diagnosis reaffirmed and and it did and these same accommodations were afforded me in college you know one thing that was kind of interesting about that I I was given

note takers in in all of my college courses and what this meant was that my my friends who were taking the classes with me could basically take their take their notes and then submit them to the accessibility office and you know they're like make a printout for me and then they would get like you know I don't like twenty dollars or something for each class so they appreciate that and certainly I appreciated it too so what did this mean it meant that I was able to be as successful as I could be as a student all the way through the end of college and that really made me feel good you know I I was a successful student I was you know achieving to the level that that I could and all of that

all of that changed one day when I graduated from college and entered the real world I no longer had the same accommodations that were afforded to me you know by law in school but I wasn't thinking about things this way and in fact I kind of landed in a lucky situation because the first job that I had out of college was at Logan hardware store which was a local hardware store in Washington DC and there I found a really good situation for myself I was on the floor helping customers every single day because it was shift work in a retail environment every task that I had to do was very small and manageable it you know whatever I was doing for a day it had to be finished by the end of

my shift no one else was going to do it and so I had small manageable tasks it was interactive work it was hands-on it was fun fright quite frankly I was using communication skills and problem-solving skills every day people would come with you know like here's a screw that I have like and I would help find the nut for it you know and like little things like that that would take five minutes and give me like little wins every day I loved that job and I really flourished there I got all the way you know in just a couple of years I got all the way to you know like the assistant manager of one of the departments in this in this store however I went to school I went to college for Computer Engineering and the bulk of like my interest in college was

in like in software development and application development and I think I always kind of wanted to get back into that and quite frankly I wanted to make more money than I was making in the retail field so I decided I'm gonna go back to I'm gonna go back into or I'm going to go into the tech industry and that's where things started to go downhill in the context of what we're talking about here today and my ad D and how it impacted my career I went through a series of jobs all right I went through a series of jobs like the first one was here in New York at a financial services company and it was a globally distributed team my manager was in Dublin Ireland the bulk of my team was

in India and the Philippines and I was like the sole developer here in in the u.s. in New York and I found myself quite isolated in that experience I very much enjoyed the people that I worked with we would you know talk over over you know Skype that kind of thing and have a lot of good good times together however that was only like a portion of my day because of the the timezone overlaps and most of the time I was alone and unable to really use that interpersonal intuition that I talked about where I could like sit next to someone and like see them face to face and understand how they're feeling and have those like really close communication also it really stifled my exuberance I was kind of alone in in this environment most of the

communication I was having was over messaging and just for the way that I work the way that I think that kind of communication just doesn't doesn't excite me in the way that this kind of communication does so fast forward a little bit to another job where I was actually starting a company I decided to start a do a startup a tech startup with another person and I was acting as like the the technical co-founder my partner was the like the CEO but I I found that that situation was extremely difficult for myself you know go back to like the the definition that I used for a DD as an executive functioning disorder like by definition the CEO although I was not the CEO of the company with two people

like we were I was doing a lot of that work and I've just told you that that kind of thinking is extremely difficult for me it's not my strength and that showed very quickly when I and one other person were trying to start and and and filled a company together a similar thing happened when I was working at the Park Slope food co-op I'm actually really excited to give this talk here in New York again because many of you may know about the Park Slope food co-op but for those of you don't it's it's essentially a grocery store but it is a cooperative and it's owned and operated by its members in order to work there you have to be a member and in order to be a sorry in

order to shop there you have to be a member and in order to be a member you have to work there for 2 hours and 45 minutes every 4 weeks it's a fascinating environment it's a very like socialist kind of structure as you can imagine it's coming from like the ideas that came out of the 60s and it's the largest one of its kind in the world 16,000 members and as the sole web developer at the Park Slope food co-op I had 16,000 stakeholders 16 thousand users and as I mentioned it was very socialist kind of structure so I also had 10 bosses that entire situation very similar to my work in the startup really made it that I had to really be on top of all of the things be very organized

you know be the product manager the designer the the engineer and I and also I had members who were using there were working for the website for their you know three hours a month and so I'm like also a project manager and all of that really was kind of like a recipe for me not to be successful so after all of these experiences plus a couple of other jobs that I haven't even thought into this is kind of the despair that I felt and I came I came to a point after the food co-op where I was really trying to figure out like what is going on like why can't I be happy in this field that I think I'm good at I enjoyed programming I enjoy a lot of aspects of engineering but I I don't

feel like I have ever been able to be successful and so I actually did at this time a retrospective I didn't know the term until until until i worked at pivot labs but I did a retro on my life on my career I saw I looked back at all of the jobs that I had and where I where I really enjoyed things that really worked well for me a lot of a lot of action item kind of came out of my work at the at the hardware store and also like what are the things that weren't working for me at that isolation that a distributed team situation being like a sole person in charge of many many things and the top action item that came from Knuth retrospective was I want to try something drastically different just run

an experiment I want to do pair programming now I had never done pair programming before in my life but I had this idea from reading a couple of articles that like maybe that would be something that could solve my problems and like let me just explain pair programming for those of you who aren't aware what this means is that you have two programmers who are working to solve one problem you got two programmers sitting side by side for ergonomic reasons we like to have to come to monitors two keyboards two mice but they're attached to one computer the displays are mirrored if I am programming if I am typing then my pair she better not be typing because we will be literally be typing on top of each other and when when I sought out an

environment where I could try out pair programming I found pivotal labs where we do pair programming you know eight hours a day every day and in fact that's what we teach our clients that's the core of our values as as as engineers and so I went to the interview which consisted of pair programming for an entire day on real projects at pivotal and I absolutely loved it I was blown away by how great of an experience I had in that one day of pair programming and since then I've been paired programming every day for three years and I've come to realize why I have come to realize why that first experience of pair programming and in fact every day a pivotal has been so powerfully enabling from me let's start with the idea of communication I mentioned that interpersonal intuition

and communication were things that are strengths of mine and by being by being able to sit side by side with someone work together constantly I'm able to communicate all throughout my day something that I wasn't able to do when I was working alone and I really enjoy that another thing that distracted nough stock with a DD is the idea that I am now accountable to someone else the chances that I sitting alone will be come distracted whether it's something external like some someone coming over and and bothering me or deciding to go look at a Facebook or Instagram or or even just like my own mind of like I'm trying to solve a problem one way and I veer off into like some rabbit hole the chances that all of those things could

happen while I'm working with someone else and they also go in the same direction are very very slim and that's what I've discovered that it's unlikely that me and my pair will get distracted in the same way together and there's one one final thing I want to talk about with pair programming is the idea of metacognition which is the act of thinking about thinking so in a modern research around attention deficit disorder there's this idea that a tactic we can use to help use to help use more of the brain especially like the frontal lobe which is where a lot of that executive functioning is happening is to use metacognition to try to think about the decisions that we're making at like a metal level and with pair programming is it is necessary to for me to constantly be in communication with my pair about

what it is that I am thinking why I'm thinking that if I have some idea and I just start typing it my pairs gonna be like what are you doing why are you doing that it's just not fair to them for me to go off on my own that's not pair of programming that's me writing code while someone else is watching so the the structure that's in place for for pair programming forces me to express my ideas out loud and the amazing thing is that if you think about it just trying to like take an idea which lives like I don't know somewhere in one part of your brain and then put it into the part of your brain that turns thought into speech that's a different part of your brain and so I'm

constantly like using a lot more of my brain in order to express my ideas out loud which which allows my pair to understand me and by extension is allowing me to be more metacognitive and I find that my brain is much more active when I'm pairing and I'm also a lot more tired at the end of the day okay so we have another core practice in engineering at pivotal labs which is test-driven development now I didn't know I knew the pivotal did test-driven development it is not why I went there I went there to try pair programming this one experiment and I discovered many other things including test-driven development so first let me tell you what this is for those of you who aren't familiar with it test-driven development is the idea that

we should never write any code without having first written a test that tells us that asserts what the behavior of our application should be to say it another way I'm always constantly writing tests that assert how I want my application to behave what the users should expect out of my application and then of course that test will fail because I have not written the code yet so that test will be failing and failing until I write enough code to make that test pass and there's a whole there's a whole discipline around how to do this but at at its highest level I'm writing the tests before I'm writing the code and I bring this I bring this up because let me take one step back before talking about test-driven development and share with you what I used to do to try to

keep myself on task before I was working at pivotal labs when I was working alone in a cubicle on a computer with the entire internet at my disposal I had to do put in place a lot of scaffolds in order to keep myself from being distracted so it's very easy for me to be distracted so some things that I would have done were put timers regular timers like maybe every 10 minutes or 20 minutes and the timer would go off and I would be like Oh am i doing the thing that I'm supposed to be doing right now and even that kind of had a problem because like sometimes I would be doing the thing I was supposed to be doing and the timer would distract me and you know it's just like

a series of painful painful moments but these were the scaffolds that I had to do in fact things that I learned from years and years of how to be a student for example now with temperature of and development is it's actually just the opposite I don't have to put in place any scaffolds in fact I I let in distractions today without any worry and here's why at any moment I can run the tests and see which tests are failing and that reminds me where I should be working and in the in the world of of like me being distracted whether it's my own brain or whether it's a product manager wants to come over and talk about some story that they've written it's it's perfectly fine by me I'll step away from the computer and

come back to it maybe even the next day I can come back and know exactly where I've left off and so I find that this scaffold that's built into the way we work is allowing me to be a more efficient programmer a more efficient employee and in fact it's just making me happier making me so I'm not worried all the time about what am I missing what am I forgetting what does this mean three years I've been doing this and over that time I felt better and better about myself compared the the way that I'm talking about working in this way compare that to how I discussed my earlier career and some of the challenges that I had there my self-worth as an engineer as an employee as a person has increased over this time and it's

allowed me to grow in ways that I really never had even imagined for example this past year I became a manager at pivotal labs and I never would have a thought that I could not only be successful in my career but be able to like share the you know like my passion for my work with others and help them grow their careers I would not have been able to do this 3 years ago without these practices that I'm talking about it's just quite amazing that my that I was able to find the place where my way of thinking matched the way that the that we work at pivotal labs and I think about the core function of my work it was always a struggle my I I was an engineer I was a software developer and the core function

of my work was writing code and I struggled in that every single day and it made my life as an engineer unmanageable but now these inadvertent accommodations such as pair programming and test-driven development they've helped me me they've helped make me just like everyone else it's kind of like leveled the playing field where I only struggle with some of the things but not all of the things like I used to it's pretty wild to think that pivotal didn't create these practices for me thirty years ago when Rob me created pivotal labs he used pair programming and test-driven development be because he believed and and I believe now as as we all do at pivotal labs that this is the best way to build software I'm I'm just like really I'm really happy that it's also the best way for me

to be building software and that's the the great takeaway that I have from my from my experience here so to go back to like the lesson that I learned that I that I'm trying to like share from this from this experience that I've had it's that I I really encourage everyone to seek out a work environment that nourishes your strengths and makes you feel valued as an individual as a human as a worker these ideas have truly made my life a lot better and I've seen the same thing with in other people and that's a message that I want to like share with with others and this this might mean seeking out a new a new job a new company that has a different kind of work environment like I did it might

mean seeking out a completely different career or it might mean working with your company with your leadership to enact changes within your organization in order to make the way you work make the way your company works better for the way that you best work I'd like to I'd like to end with one more story there's something there's something here that's quite important the idea of empathy empathy for other people it's critically important when pair programming I mean you have to work eight hours a day with another person you need to be empathetic of of their need and their desires their thoughts absolutely oh and it's and and to the message of what I was trying to share there's another part of empathy that I think is really important so I'm gonna share a quick story my wife and I went

to a workshop actually at the Park Slope food co-op a member of the food co-op she hosted a workshop for couples where one of the couple was had a DD and and spoiler like I I'm the person who has a DD in our relationship and in the workshop we we didn't exercise where we listed all the things are a bunch of things that we appreciated about our partner on one side and on the other side we listed a number of traits that we found particularly annoying about our partner and then we were asked to draw lines between like one trade on the left and a trait on the right and try to make a connection between things that annoyed us and things that that we appreciated so for example my wife said that she

appreciated that I'm I'm good at figuring out how things work she's very very kind of her but she also finds it very annoying and in a related way that I like to touch everything so how this plays out when we go and rent a car we will rent a car at the airport pick it up and they'll in the lot and she gets in you know I guess like usually usually I'm probably driving right so she gets in the passenger seat and she you know she puts her coat away buckles up and she's ready she's ready to go I get in and like it's like 10 minutes of fiddling with the windshield wipers and the lights and and buttons and like I got a pair my phone to the Bluetooth and you know I take out maybe the owner's

manual of the car and it's like a whole ordeal and as time goes on you know minutes are passing and she's getting more and more frustrated and this is a pattern that we have but what we'll often what what can happen here is that half an hour later we'll be driving down on the highway and she finds herself maybe uncomfortable in her seat and she's like trying to figure out like how do i how do I make myself comfortable and I'm like oh well you just gotta press the one button over there to like adjust your seat and she's like oh like how'd you know that and it's this it's this story that kind of like makes me makes me realize and this is where the empathy comes into play that it's important you know whether in in a couple like me and my

wife or on a team at work that we rely heavily on each other's strengths and focus on that and be empathetic about how each other works all of us approach problems differently which at times can be really frustrating but what frustrates us in one moment might become an asset in a different situation you know every person that you meet every person on your team we all have unique ways of thinking and unique ways of learning and next time you're finding yourself getting a little bit frustrated with your team members just remember that thought that you know what everyone's think everyone has a different way of thinking but we're all valuable members of the team okay thank you that that's what I had to share for you today and I think we're going to answer some questions

so you just recently out great job I really learned a lot this is really interesting I don't have a DD but I find this interesting if I didn't work with people of the EDD so this is great to know and something I can think about so you just recently went into a management position correct so how does that transmit transition been from pair programming if you still do it to management and how it was that been like at this company yeah thank you I really appreciate that question I died I realized now that that's that's really good feedback so let me be clear on on what my my new role is like you know 85% 90% of my job is exactly the same as it was is pair programming test-driven development every day consulting with

clients like teaching our clients how to do these practices and that other 10 15% maybe maybe more it probably adds up to more than 100 percent now is is the management part and the way you know like the way management works a pivotal is so I'm mostly an individual contributor and I have several reports and I work with them to help them grow their careers give them advice help help them get feedback from other people feedback from their clients and so on so that that's the structure of my my new job my new role which is just a little slightly different it's basically the same in my old role but with with some added responsibilities as a manager but I would like to I would like to like be honest with everyone that the reality is that being a manager this past year has

been very much a challenge for me a lot of the aspects of management are are like heading into the direction of some of the things that I talked about the idea that I am kind of isolated like I am alone the manager for my six reports and there's you know there's certainly I can work with other managers I can pair with other managers on my team to you know get ideas and you know maybe get feedback on on things that I'm doing but like the bulk of the work like comes comes down to me it's not like I am a team of managers working with my reports and that's definitely something I'm I'm missing and it's been a challenge I think it's a challenge that I'm excited about because there's so much about management that is just like warms my heart

you know the idea of servant leadership and like giving of myself to another person to like help them grow and in seek out you know seek out an environment that nourishes their strengths help them create an environment their nourish as their strengths do the things that I can do within my power to make sure that our DC office is an environment that nourishes the strength of the people in the office these are really fulfilling statements that I'm making but the reality is it's it's hard you know I'm back into the same the same ideas of like working alone towards goals and there's a lot of task oriented executive functioning kind of things that I have to do so yeah it's a challenge it's an ongoing story you know like maybe maybe next year we'll we'll be talking telling a different story I don't know

this is all really cool to hear about I'm it sounds really interesting that sort of just a best practice in like life practice ended up being best practice for everyone so the more inclusive you are in the way that you design your practice the more people benefit from it which sounds like really what happened I'm really curious you talked about there being scaffolds built-in that you didn't have to make for yourself they're just built into the process of how you are doing your work I'm curious if you've seen other types of work that have those kind of built in scaffolds in other places or with other clients that you've worked that kind of mimic that cuz I think that's a really interesting thing it just seems like it's built into the workflow so it's not

a separate kind of accommodation it's just there I'm curious if you have other examples of that in places yeah so I'm trying to think of and I'm really trying hard to think of an example outside of the like my experience at pivotal and I'm coming up short right now I'm sure that there are like this is not the only way to work as much as ill it seems like the only way to work for me but but that that's not the lesson that I'm trying to share that like everyone should be pair programming I think there's other I can I can share like within within the lens of like a balanced team a pivotal product managers and designers and engineers so I mentioned that executive functioning like the idea of like having

having tasks and doing them in a certain order and like making decisions around that that can be a challenge for me so the way that we the way that we do agile is with extremely small stories very thin slices of work and so each story could be you know like ideally is something that you know although we don't estimate by time like it's ideally something that takes less than a day to if if we can manage that and so I rely on the product managers to write those stories in a very very small way with a lot of detail a lot of detail around you know like these are the two scenarios that when you're done with your story the the application will now have you know like these two scenarios covered

and I I in fact have have tried to be a product manager at pivotal EPS there was a project that I was on for about a month that we didn't have a product manager and and so I stepped into that role and I found it extremely challenging and the most challenging part of it was to for me to like create that scaffold to create those stories with with like the task of like it's got to do this and this and this for the other engineers and I realized now like kind of in the context of where you're talking about I am relying heavily on the organizational skills of our product managers in order to give me work that I can do within like within my abilities to do it because the alternative to that

which is which is what I've done in the past is someone saying like you know here's a requirement like you you got to build an app that that has a login and that is like way too much for my brain to breakdown alone you know I need to work with other people to you know create that scaffold for me if like here are 10 stories that represent the the epic of a login page and I'm just gonna do the first story and I don't have to worry about those other stories because I'm I'm just doing this first story and it's like there's you know there there's a button on the page and I can do that I can make a button on the page but what I can't do is make a login page because that requires organizing into ten

different steps doing those steps in order and like that's just not where my strengths lie any other questions in the room I'd say yeah I have a two-part question one is relating to the practice of pair programming and productivity I wonder if you have any if or if you you have for you either you or pivotal labs there's any sort of case studies or anything empirical sort of supporting pair programming in some of these practices that's show that productivity other increases or bug counts decrease most of the studies I've seen on it suggests that pair programming really gets you to the velocity of the higher performer of the pair as opposed to raising the net performance of two people and along those same lines the second part of that question is how do you find pairs that are really

complementary and that allow people to get along together very well like I haven't had super extensive experience with pair programming at least not in a corporate setting but it seems like from the pair's I've seen it either is like very hit-or-miss so how do you kind of optimize for that and or do you let it grow organically or yeah what would you say about that okay sure I'll ask you to just hold on to the mic for a second because sure let me start with the first part of that question so the first part of that question is about pair programming and productivity yeah so there definitely have have been studies about pair programming and productivity I'm not very good at like remembering the details of something like a study or anything like that but you know maybe maybe afterwards we can like we could

look something up together but more broadly like here's here's how I I look at it and not me alone like this is this is certainly like pivotal labs view of things right that when you have to people working on problem together you for one you your you're not gonna have to do any code review so you've already eliminated this like the extra time that it takes to do code review because you've got to eyes on the problem at all times its instantaneous code review that's one of the big reasons why we do this additionally you you're like constantly like thinking doing that metacognition thinking about your thinking working with another person it's necessarily going to increase the quality of the code that the two people are producing even even an extremely high performing programmer working with a very very

junior person in like the worst kind of situation where like the high-performing programmer is just doing a lot of typing and the junior programmer is just watching which by the way that is not how we should do pair programming but even in that situation the junior the junior programmer is is going to notice things that the high performer likely that the very senior programmer you know may make like you know small mistakes in the moment or the junior person will ask question now we're getting into like how pair programming really should work the junior person is going to ask a lot of questions about like well why do we do this you know like how does the work tell me the context right and now you've got the senior person like answering questions about this sharing that

context and it's it's creating like extra metacognition for that senior person right there's also the idea of like you know like what's unfortunately called the bus count or like I like to call it the lottery count right so you've got a senior programmer who's been on this team for 10 years and is the only person who knows this part of the system if that person wins the lottery and leaves the company the whole team just stops in velocity with pair programming the way the way we work if right now I'm actually on an extremely large team with five pairs so we have 10 engineers that's huge but more typically let's say we have three pair to three pairs of engineers so in three pairs we've got six engineers and every day we're pairing we're rotating our pairs so I'm pairing with a different person every

day and with a three pair project I can easily every week visit every every bit of of code that's being worked on and so every one of those six people has full context on that application if someone's sick no problem if two people are sick no problem if four people are sick or four people are on vacation no problem the team slows down certainly but you still got one pair that can do anything can pick up any story on the backlog and work on it so this is my way of saying that it's more than just how fast can a developer or a pair of developers go there's many other factors that I you know that go just that go beyond just the team that you got to think about like at a business level and oh I could

talk about this you know this is my job I could talk about this for four all night but let me let me get to your other question if you could remind me oh yeah the other question was just trying to maximize the complementarity of the workers so that they can work well together and like I guess when you look at high-performing pairs as opposed to just like individuals like what characteristics or qualities show up most frequently I think I will say this you know pair programming is not for everyone it does it takes a lot of empathy to to pair all day with another human being to to work with someone so closely and you know care about what they're what they're thinking you know care when you know so like let's say let's say

I am a very senior engineer I've been on this project for a while I can move pretty fast because I know this system whatever if I have a brand new junior person who just joined the team right I have to have a lot of empathy for that person's situation I have to understand like they're new they're eager they want to learn so I'm gonna have to go slower in order to help them learn and grow to the point where they finally can move a lot faster and that's the kind of thing like that's the kind of trait that's needed that empathy that that patience that caring you know and to different degrees right like some people are extremely empathetic and make amazing pairs some people have differing levels of empathy and still make good pairs maybe not as amazing as that first

person I talked about so there's yeah there's there's i I can't stress enough how important empathy is yeah I think I think that's the most important trait that's this needed additionally I think like this idea of rotating around really helps a lot there are times when you have just two people on a project and they're just you know we call that like pair married to each other the entire length of a project you know in that situation if they are not if they're not compatible with each other and willing to give each other feedback in order to or willing to give each other feedback to make them more compatible for each other then it's going to be maybe a little bit painful process whereas if you have these three pairs six people and you're like only once every five

days am i working with the one person who maybe doesn't I'm not as compatible with like that that's a little bit less of a severe situation and that thing about feedback that's the other like most important thing is that people who are pairing have to be willing to give each other feedback accept feedback have very short feedback loops so that they can grow and be better pairs and and help other people be better pairs to to them or else the systems not gonna work for them does that answer your question yeah that's pretty good thanks hi so I heard you talk about like working at Logan and your love for this kind of true human connection and being with other people and you know I see that you know you also had trouble with executive

functioning and then now your manager and so I just imagine being a manager involves a lot of it could you talk a little bit about like was this like a process that was more like I've evolved into this role or it was it something that you just came to fine within you like that I already had interesting it's the answer is probably more to the second thing you've said like that it's something within me that I always had but but like there was never a space for it so you know let's look at the example of when I was working for that distributed team with the my team in India and the Philippines and my manager in in Ireland right in that situation I was like just struggling to get by you

know like just struggling to be you know I want to say like just be an effective developer on that team even that was a stretch honestly so there was just no space for me to also consider like oh well like I really care deeply about my team members in India for example you know like I I loved working with them I loved hearing about like the things that they were learning and the things that they were working on you know one of what I like honestly would like my biggest regrets in life was leaving that job just a few like a few months before one of my co-workers got married and I was like so excited and like thinking about going to that wedding but you know because I left that job and was at another job I just think it just didn't

work out so all of this to say that like I think all of the things that make me all the things that make me a good manager today well they all existed then like the same traits that that caring like that desire for a servant leadership but like I I just there was no space for that like I really I think you know like I another way to put it is like in order to in order to succeed or in order to grow in in in a different way from from like the core function of your job so like the core function of my job is writing code and being a consultant and in order to grow in any way beyond that so for example I am particularly skilled in coordinated in like strategy in my

job like strategy amongst like several teams when several teams are trying to figure out like how do we prioritize work across several teams that's something that I found like I'm very good at but I never would have had an opportunity to even know I was good at that and no one at work would have given me the opportunity to do that if I wasn't at least good and a bay line weigh at that core function of my job and it's the same with with management no matter how empathetic I am no matter how caring I am about growing other people if I was not a good engineer I would not have been able to get that promotion or even like really realized that I would want to do that because I would have been just like kind

of treading water which is what I did most of my career thank you any other questions great well thank you Matthew thank you kind of applause so well I'll just add one more thing so you know like pivotal labs is is hiring so if some of the things that I've talked about pair programming test-driven development if if any of that is interesting to you please reach out to me and I'd love to talk more about that and and also if some of our other practices like product management and product design if those things interest you we'd be we'd love to you know have you come out and check out the office and stuff like that thank you nice so we've got about 30 minutes or so to stick around if you want to mingle with folks talk about jobs with with Matthew that'd be great

thanks to jolly again for handling the the live stream and to Diana for the captioning tonight and to thoughtbot for hosting all right that's it