[sodapopcan]

I did 100% pair programming with a team that didn't standardize on editors or keyboards. We solved the issue in the article by just never using each other's machines. It was very rare that the navigator would want to type something but if they did, it was usually just a line or so, so we would "strong" pair, ie, tell the other person exactly what to type. If we wanted to switch the driver/navigator role, we would just make a WIP commit, force-push, then pull and `git reset head^`. It was only ever two people working on a branch at a time, so the force pushes weren't scary. We did this without issue for three years.

[PartiallyTyped]

Unfortunately my employer doesn't allow force-pushing :(

Instead we resort to using jetbrains stuff.

[diarrhea]

Same at my place. I think it’s for compliance reasons, but it feels patronising. A bit like taking away the sharp tools so us dummies cannot hurt ourselves. Next, maybe No-Code GUI programming because a real language is too scary too?

[sodapopcan]

I understand not allowing force-pushing on main, but pretty weird for branches you own and no one else uses.

[kartoshechka]

golang almost accomplished to be non scary language, but the users have been fighting back