A place for developers to talk about building on Farcaster.

/dev

What are your thoughts/experiences with pair programming (with humans)?

I've never done it. I always fund the idea of it quite wasteful.

I find code reviews significantly better since they're asynchronous, can involve more than two people and it all gets documented so knowledge transfer is significantly higher than pair programming.

The open web is dead, long live the open web. ⌐◨-◨

Building /warpcast and /farcaster

— gabrielayuso.com

what was/is your code culture that made PRs successful? did leadership push it or set by the teams?

👨‍💻 /uno and /outside, @unofficial

For spreading context around what the code does. I think a light weight design review process can help even more than code reviews.

For code reviews at Google there were policies around language readability, code ownership and not being able to submit code unilaterally even if you're the owner and have readability.

I liked both requiring the owner stamp and the readability stamp not necessarily the unilateral policy.

The readability process was good since it helped learn best practices. The owner stamp  was good because the owner could share their context and ensure the new code fit well and didn't make wrong assumptions.