4 ms·
How many startups here use pairing? Anecdotal evidence tells me its mostly used by consultancies (Pivotal Labs and Hashrocket are others that come to mind).
by bentlegen 15y ago
How many startups here use pairing? Anecdotal evidence tells me its mostly used by consultancies (Pivotal Labs and Hashrocket are others that come to mind).
- squirrel 15y agoTIMGroup do, and we are a product company, not a consultancy. (We don't use it exclusively, but certainly pair very frequently.)
- zbrock 15y agoWe pair a fair bit at Square. We require that all code either be paired on or go through code review, but let each team decide their own process. Some of the teams pair 90+% of the time, and some pair only infrequently.
- technomancy 15y agoWe used it all the time (Emacs/SSH/tmux) at my last gig since the engineering team was 100% remote. It worked fantastically well.
- dylanz 15y agoWe (a consultancy) seem to only use it when someone has some design/implementation questions and/or concerns. For example, I don't need someone watching me write code I'm comfortable writing... they should be busy producing as well. However, if I'm unsure about something, having someone look over my code and/or help code, is extremely useful. Code reviews is a different subject completely, and is "definitely" a great learning experience for everyone involved.
- matthewcford 15y agoThat is because pairing helps mitigate risks (human error), when you're being paid to build software no client like to pay for bug fixing, they would rather pay a bit more to make sure there are less errors (or at least appear more bug free). If you're a bootstrapped start-up, it is not an efficient use of time to be pairing 100% of the time. We tend to only pair on 'core' parts of apps or 'hard' problems, or when someone needs another pair of eyes on something (two heads etc), otherwise clients budgets are quickly exhausted on pairing for pairing's sake.