search

USRSE / monthly-community-calls

Location for gathering community call topics
MIT License
4 stars 0 forks source link

RSE Team Member Interaction #3

Open christophernhill opened 3 years ago

christophernhill commented 3 years ago

Mahmood M. Shad: In small RSE teams, software developers may work independently on projects while their share skillsets. The discussion is around how developers within a team effectively interact with each other or work on multiple projects.

vsoch commented 3 years ago

I like this topic too. I've recently started working on a team and really love the dynamic - enough independence to make progress on your own, but a supportive structure of people that care about what you are doing to ask questions, and discuss how things fit together, and the next exciting thing to do!

omsai commented 3 years ago

I would like to hear about stories of practicing code review in small teams:

  1. How often: weekly, monthly?
  2. How many lines of code can reasonably be covered in 1/2 or 1 hour,
  3. Checklists used to guide the discussion,
  4. Any cases of going beyond the internal team to also take this up at the larger core facility level, and how that can plays into a typical data science consulting workflow.
nickdelgrosso commented 3 years ago

Hi, I'd like to contribute to this discussion; there are a few patterns I've found based around pair/mob programming and testing that work really well and encourage repeated and continuous close collaborations.

NickleDave commented 3 years ago

Sounds like some of this overlaps with #9

I would definitely be interested to hear more along the lines of what @nickdelgrosso and @omsai commented on

Maybe I could take some notes and bring back to https://github.com/ResearchCodeReviewCommunity Recently talked with someone about when/where pair programming can achieve many of the same goals as code review