Timeline for Pair Programming/Collaboration in a small company
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot |
replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
|
|
| Aug 25, 2013 at 2:13 | comment | added | Ryan Williams | Also, to be clear, I wasn't talking about pair programming as something we do all the time. Rather, devote some significant, but not huge portion of the work week to it for larger or more complex features. (That's partially out of practical necessity. I have my own demands that need to be met.) | |
| Aug 25, 2013 at 2:11 | comment | added | Ryan Williams | Seems to be a popular opinion. I like the idea of code reviews. But in my mind I would guess that with their personalities and skill levels, it's going to be me who is doing the reviewing, and them just listening (mostly uninvolved). But maybe there is a way to get them more involved. I guess I have to reflect on that. | |
| Aug 25, 2013 at 2:02 | history | answered | Thomas Owens♦ | CC BY-SA 3.0 |