undefined | Better HN

0 pointsdilyevsky4y ago0 comments

Your answer is basically just use async process which was already a thing before pandemic and it sucked then

0 comments

That's not exactly my answer.

One of the things that I think remote work changes is that traditional power is diminished. If you are used to forcing people to have contentious discussions where you win your favored outcome, that may be the wrong framework.

After all, "design" in software is really just making a lot of small choices consistently. Arguing people into a decision is one way to get consistency, but far from the only one.

dilyevskyOP4y ago

Not really about “winning” but about having everyone on the same page. And yes you can do it async too but it’s more difficult. The result I think is more likely to evolve into either a bdfl style arrangement or everyone pulls in their own direction.

wpietri4y ago

I agree other ways are more difficult if you aren't used to them. And some other ways may be more difficult for you personally. But I disagree you can universalize your feelings here.

I've been part of in-person pair programming teams that had frequent pair rotation. We only rarely had meetings, and never had any formal design meetings with pitching and persuasion and whatnot. All our communications were synchronous and high bandwidth, but our design choices happened gradually and over time. It worked fine. Better, really.

j / k navigate · click thread line to collapse

0 comments

wpietri4y ago

That's not exactly my answer.

After all, "design" in software is really just making a lot of small choices consistently. Arguing people into a decision is one way to get consistency, but far from the only one.

dilyevskyOP4y ago

wpietri4y ago

I agree other ways are more difficult if you aren't used to them. And some other ways may be more difficult for you personally. But I disagree you can universalize your feelings here.

j / k navigate · click thread line to collapse