Notes on software

On shipping

  • optimize for fast delivery

    • smaller changes released more often
    • faster deployment process
  • smaller changes usually means bugs with less impact

    • but could be more smaller bugs
  • delay in delivery brings anxiety

    • each new WIP-line make you more afraid of delivery
    • bigger changes - slower code review / more tokens per PR (but less PRs, so maybe shouldn’t bother)
    • delivery becomes big event with wider consequences - they cover more areas
  • release is final (opening) delivery of the task / user store / feature
  • smaller changes maybe have small impact on long-running processes

    • you can have invoicing once a month and see impact on the day
    • these processes needs shorter loops to monitor correctness

      • even you invoice once a month you can collect what to invoice on daily basis and check how they look

About

Jan Filipowski - Ruby developer, team lead and architect