re: Developer eXperience: a feedback loop VIEW POST

FULL DISCUSSION
 

Used to work somewhere where the CI suite would take 1hr+. So even though each individual developer could not do much during the day we still would ship 50+ PRs per day.

I think in a large enough organization the scale is different and personal productivity must give way to organizational throughput. Sometimes these things are at odds and optimizing for organizational throughput is the correct approach.

 

Some things are mixed up, let's clear up

  • PRs ≠ feedback loops
  • PRs can be different, really depends how organization slice tickets

Typically in case of big test suite people use "focus" feature e.g. run test suites only related to the part they change, and if they lucky enough they get isolated part, so running this test suite is enough (this way feedback loop is a bit smaller). Then they commit it and hope it will not break in CI. While test runs, people switch to something else, to the next ticket for example, and then can happen that CI is broken and they need to switch context back to fix it.

Or different approach, people simply give up TDD - they just code everything without running tests and come back to PR only if CI fails.

Does it sound familiar?

 
code of conduct - report abuse