[sshine]

I have colleagues who move fast, break things, and don’t believe in interfaces. They are highly productive and it’s hard to cooperate with them in any other setting than pair programming, which does work great.

Then I have colleagues who write the interface first, tests second, and finally write code.

Cooperation between these cultures is hard. It works best to have cycles between areas of a code base. The interfacers can easily end up as janitors and cleaners, and there can be friction.

I think both styles are warranted, especially in startups.

[drakonka]

I like working with the "move fast and break things" people if they take my feedback into account when it comes time for the "cleaning" or PR review, AND if they have the time to properly address the feedback vs just being pressured to ship immediately.

[throwaway_bags]

Thanks, this is a very balanced answer.

It reminds me of the testing versus debugging: some folks are great at testing code so it never breaks, others are better at churning out code and debugging it as they go.