3 ms·

> think most of us would have flipped. No. At my current job we pair program using a zoom call for everything with the person writing the code sharing his sc

by LandR 2y ago

> think most of us would have flipped. No. At my current job we pair program using a zoom call for everything with the person writing the code sharing his screen. Sometimes there can be 4 or 5 of us on the call. We are far more productive than any place else I've worked.

deleted 2y ago
[deleted]
wruza 2y ago
I wonder how many psychological effects it has that AI-pairing will not have. The fact that you have to write the f-ing code right now alone changes everything. I guess you can ignore impulses to overcomplicate things much more easily? The code becomes unclever and accessible to everyone on the call? We are far more productive than any place else I've worked. Divided by 4-5 or that’s per person?
- LandR 2y ago
  > The code becomes unclever and accessible to everyone on the call? Yep, bullshit gets called out immediately. > Divided by 4-5 or that’s per person? Compared to other places, I'd say what took teams much bigger than us weeks or months we can do in a days. But we have very little bullshit standing in our way, we work in 2 day sprints, but without all this sprint ceremonies. No retros, no standups, no kanbans, no story boards points. It's just "here's a business problem, you've got 2 days go make us a solution". After 2 days we can demo it, and if its good enough then we can move onto the next highest priority problem, or maybe the solution does X,Y and Z but then they decide they'd also like A, B and C we can keep working on it. We also have our SME / PO on the call with us all day too, so we can get immediate feedback from them as we are dev'ing. EVerything is centered around having little no time between us actually doing the dev work and getting feedback on it. We can iterate really fast. And because we have multiple devs on the call, we don't need PRs or code reviews. Some developers absolutely hate this setup though, and just seem unable to code when other people are watching.
  - wruza 2y ago
    Thanks for sharing, interesting! Some developers absolutely hate this setup though, and just seem unable to code when other people are watching. It passes with time, but yeah, onboarding some of them to this group must be impossible. I knew some “quantum” guys who couldn’t move while someone watches. Also highly correlates with bikeshedding. It’s usually confidence-related anxiety that should be addressed either way.
  - dgunay 2y ago
    This is what real Extreme Programming looks like. Still haven't been anywhere that truly embraces the less popular aspects (pair programming, very short feedback cycles, direct customer involvement).

by LandR 2y ago

deleted 2y ago

[deleted]

wruza 2y ago

I wonder how many psychological effects it has that AI-pairing will not have. The fact that you have to write the f-ing code right now alone changes everything. I guess you can ignore impulses to overcomplicate things much more easily? The code becomes unclever and accessible to everyone on the call? We are far more productive than any place else I've worked. Divided by 4-5 or that’s per person?

LandR 2y ago
> The code becomes unclever and accessible to everyone on the call? Yep, bullshit gets called out immediately. > Divided by 4-5 or that’s per person? Compared to other places, I'd say what took teams much bigger than us weeks or months we can do in a days. But we have very little bullshit standing in our way, we work in 2 day sprints, but without all this sprint ceremonies. No retros, no standups, no kanbans, no story boards points. It's just "here's a business problem, you've got 2 days go make us a solution". After 2 days we can demo it, and if its good enough then we can move onto the next highest priority problem, or maybe the solution does X,Y and Z but then they decide they'd also like A, B and C we can keep working on it. We also have our SME / PO on the call with us all day too, so we can get immediate feedback from them as we are dev'ing. EVerything is centered around having little no time between us actually doing the dev work and getting feedback on it. We can iterate really fast. And because we have multiple devs on the call, we don't need PRs or code reviews. Some developers absolutely hate this setup though, and just seem unable to code when other people are watching.
- wruza 2y ago
  Thanks for sharing, interesting! Some developers absolutely hate this setup though, and just seem unable to code when other people are watching. It passes with time, but yeah, onboarding some of them to this group must be impossible. I knew some “quantum” guys who couldn’t move while someone watches. Also highly correlates with bikeshedding. It’s usually confidence-related anxiety that should be addressed either way.
- dgunay 2y ago
  This is what real Extreme Programming looks like. Still haven't been anywhere that truly embraces the less popular aspects (pair programming, very short feedback cycles, direct customer involvement).