Team Collaboration and Pair Programming

Video conference

Google Meeting and Slack Call are both great conferencing tools for collaboration (Google is more stable and sound quality is better, but Slack lets you draw on the shared screen and is easier to jump into and out of). Announce your meeting in the slack thread if using google meet, otherwise use the huddle in #devsecops. It will help other team members to decide whether it is an interesting topic to them and join the meeting.

TMUX (No longer in use, FCS only directions)

In addition to keep your session live even after being accidentally disconnected, TMUX is also a great tool for collaboration and pair programming. Here is some common practice we have been doing on Sandbox and BSP environments that I found useful.

1. There should always be one common TMUX session for Ubuntu user. So after a user log into jumpbox and assume Ubuntu role, always run tmux a command to attach to the common session. If for some reason there is no existing session, create a new one by running tmux. Sticking to one common TMUX session will let users aware of each other's presence, and prevent any potential conflicts and surprises.

2. After connecting to an existing TMUX session, if you see the terminal is idling, you can check other users's presence by running shell command who and TMUX command ctrl-b D. It will give the info about which user is connecting to the session and how long since last activity. Communicate with the other user on Slack if you have any doubt about whether you should take control of the session.

3. For pair programming, TMUX allows multiple users type in the same session. So start a conference call and let us pair.