3 ms·
this is not much different from pair programming. even pairing with a junior developer where i do most of the work myself makes me more productive. pair-progra
by em-bee 8y ago
this is not much different from pair programming.
even pairing with a junior developer where i do most of the work myself makes me more productive.
pair-programming is also exhausting. after an 8-hour work day i am beat. however i can't think of any better way to work, and it it is practiced in several companies successfully.
if people would want to quit after a week or kill themselves after a month of pair programming we would see a lot of backslash against it.
- ui-explorer12 8y ago>> if people would want to quit after a week or kill themselves after a month of pair programming we would see a lot of backslash against it. That's been my experience. Even at the few places I've been were some do pair programming it's a very rare occurrence. Occasionally upper management will stump for it, likely because they (a) don't actually program all day and (b) see it as some sort of kale-like super habit. None of my IC have ever pushed hard for regular sessions.
- l0b0 8y agoWe pair programmed more than 90% at my last job, and it was great. Together we would typically come up with architecture, design, tests and names which were better than either of us would have done on our own. It is hard work, but very rewarding, and it has many pitfalls and nuances which we tried to work out at our ~fortnightly review sessions. More important than pair programming itself is the willingness to look at what works for the team and how you can improve the experience and productivity together. Most of the time we did traditional pairing, with two keyboards and mice on a dual-monitor PC, and simply signalled each other when we wanted to take over or cede control. Towards the end of the four years there we very successfully "mobbed" on some complex problems, and split up when we had worked out what to do next. We would typically work in different pairs every day, which resulted in everybody knowing the entire system to a similar degree — we didn't even need a handover when someone left, and onboarding basically meant that the more senior employee had to explain a bit more of the context while pairing with the new hire. I found it did wonders to my understanding of how other developers think and especially how to explain my thinking to someone else. But YMMV, and good luck!