That’s where one of Jason’s other principles—opt in to complexity—comes into play. While teams can take the default settings, they can also dive into the bowels of Admiral, and rewire it for the particulars of their project. Don’t like the default unit testing framework? Developers can plug in their own, while still keeping all the benefits of Admiral and the rest of the pipeline. The same goes for all components. This gives teams autonomy to pick their tools, while making the defaults easy and attractive, helping to encourage adoption of Admiral.
