Hi, Dagger co-founder here. Dagger is really just a streamlined implementation of two very common patterns: 1) Keeping your CI configuration as light and "dum

Hi, Dagger co-founder here. Dagger is really just a streamlined implementation of two very common patterns: 1) Keeping your CI configuration as light and "dumb" as possible, by moving as much logic as possible into portable scripts. This minimizes "push and pray", where any pipeline change requires committing, pushing, and waiting for the proprietary CI black box to give you a green or red light. Ideally those scripts use containers for maximum reproduceability. 2) Replacing artisanal shell scripts, Makefiles and arcane DSLs with regular code, backed by a modern API. This allows using modern development techniques, a broader ecosystem of tools, and growing the pool of people on the team who can understand and improve the pipelines they use. To many devops teams, these patterns are just common sense, an everyday reality. For others, they are aspirational: maybe one day, if we find the time... Implementations remain very custom. Our goal at Dagger is to help democratize this way of creating pipelines, and making it a standard, so that an actual software ecosystem can appear, where devops engineers can actually reuse each other's code, the same way application developers can.