3 ms·

Am I really the only one on this forum to think that live shared coding is a terrible idea? The only pro for this is there are no conflicts, so merging is easi

• djsumdog 9y ago
  I've only done direct pairing twice. It can help come up with a game plan and get new people in the company up to speed, but it is terribly terrible stressful. I don't like it. I think small services, incremental changes, strong tests and solid code reviews all work much better. Especially the tests and code reviews. At my last shop the company had an internal Gitlab and we used the Gitlab CI. Reviews + CI really helped keep the coding standards pretty high and helped younger devs not make beginner Scala mistakes coming from a Java background.
• drvdevd 9y ago
  IMO coding out of sync is one of the main useful functions of all modern DVCS systems. Coding together can be useful or fun, I'm sure, but I've noticed that other people don't enjoy my coding style very much in a group setting. I like to just sit there and read through the code for a long time to figure out how it works, maybe throw in a print statement here or there, and reason out loud about it (or mumble about it myself). Most people like to step through interactively and debug together, and in a group setting this can become a real conflict in my experience.