Fork me on GitHub

I wonder, is there a clojure-based organization that values (remote) pair programming as a productivity tool? Basically, that thinks that in some circumstances pairing is the most productive arrangement for two developers?


I can vouch for They value pair programming a lot for all the good reasons. I have been working remotely since the pandemic and using pair programming and ping pong. While is a highly distributed polyglot environment, there's a lot of Clojure across the organisation (and regardless of the programming language, pair programming is advocated for).


In Flexiana we do fairly often remote pair programming. I think the main difference from classic approach is committing when the code is WIP when handing over to a colleague because people to have highly customised (not only) Emacs setups.


thanks @jiriknesl, I mostly mean, what's the way the organizational culture looks upon pairing? Is the culture enthusiastically encouraging that, or is it "when you're stuck pair a little and then back to solo work"?


It depends on a culture. People here are hired as craftsmen and are encouraged to do TDD, write clean code, refactor and pair. Elsewhere it could be different.

Jivago Alves13:10:32

I can’t speak for the whole company but in the business unit I’m located at all the teams use pair programming as default and “break pairs” when it makes sense,

Jivago Alves13:10:30

Company is not Clojure-based but my team specifically is working with Clojure.

Jivago Alves13:10:50

Pair programming (along with TDD, etc) was built-in since the beginning of the BU.


The company I work for does pair programming almost all the time. We do have solo time when someone is out, or the pairs are uneven and we get time to do open source or personal career education Friday afternoons.