> how adamant the typical HN'er is about having good commit messages, and follow a strict merging paradigm, such as peer reviewed pull requests That’s communic

> how adamant the typical HN'er is about having good commit messages, and follow a strict merging paradigm, such as peer reviewed pull requests That’s communication, and sometimes a protocol helps nicely in getting the relevant information out of the medium. Especially when the communication is async as everyone knows roundtrips is bad. > with lot's of room for discussing minute details of rebasing versus merging with or without squashing That’s geeky time out of work. When doing it, we know that we’re not working. > a shared to-do list across a team The shared list is not the issue. It’s what happens to the items inside it. Scrum make us work more on the item organization than what it’s worth. Then they get arranged into something that doesn’t really matter (sprint), and then we are judged on that. While we just want to get things done.