In software engineering, continuous integration is common practice nowadays. Common CI setups have a few drawbacks. This talk highlights them and introduces a different approach with additional benefits.
Many projects will operate on the premise that there is merit in an "evergreen" main (git) branch, i.e. that for each of the commits on that branch passed some CI jobs.
Common CI setups will schedule runs for a number of jobs for newly created or updated branch tips in some development repository, including the main branch. However, the latter will only be tested after the merge is done and that test may fail.
The speaker proposes a different workflow which avoids this problem and, in theory, introduces opportunities to safe operational costs by requiring less CI runs overall.