re: What are your guiding principles in software development? VIEW POST

VIEW FULL DISCUSSION
 

The team must understand all changes. Together we stand.

We pair to ensure shared code-knowledge and no “waiting for review” queues, and I advocate for isolated PRs so other devs can look at closed PRs and make sense of recent changes. It’s tempting to push unrelated changes into your ongoing PR to save time but it confuses every time.

By isolated I mean a PR should have a simple, understandable title, it’s changes should all relate to that, and the size should be small enough that no one sighs when they see it.

code of conduct - report abuse