"What leads to #code review anxiety? Our model shows that we can intervene on code review anxiety by targeting the cost bias (when we overestimate the "cost" of a negative outcome) and anxiety self-efficacy (our belief in our ability to tolerate and manage anxiety), with anxiety self-efficacy being the strongest contributor to code review anxiety."
@tim_abell@CSLee@seresearchers
I'm in IT for 25 years and it still makes me uncomfortable. I somehow want people to see only the end result, not my struggle to get there.
@goleztrol@tim_abell@seresearchers you’re not alone! A big misconception is that this only happens to inexperienced devs or during asynch comms anxiety impacts folks regardless of experience (our sample had folks with 1-65 yrs of experience and experience was not significantly related to anxiety), during asynch and synch comm, etc.
@tim_abell@goleztrol@CSLee@seresearchers i have 10+ years of dev experience and pairing sounds like hell on earth to me, actually. I know some people love it and get a lot of value of it out but shudder
@thatandromeda@goleztrol@CSLee@seresearchers it produces better team output; professionally we're here to do a job so if that's part if it then we just do it. I personally thrive on it.
@tim_abell@goleztrol@CSLee@seresearchers It is great that you thrive on it! I have declined to interview at a company that was very pair-programming-oriented. I respect that it can produce better output for many teams but for me personally I would shut down and produce essentially nothing at all.
In some cases me being nervous can actually make a junior dev feel more at ease, less intimidated, so the total level of uncomfort is still the same ig 😁
Add comment