> you're going to want to develop complex pipelines and build processes to help with development and testing

Opinion: Complex build processes are great. Complex _pipelines_ are a trap. I'm in a position to see the output of a lot of teams at a very large company. The teams that have complex build processes _that they can run locally_, and then have some trivial CI yaml to run the build, are doing great.

The teams that designed their build around CI are brittle and eventually end up in a state where they can _only_ do some parts of their build on CI.

IME it's worth it to set very hard boundaries shaped like: (1) Everything needs to be able to be run locally (usually in a devcontainer), (2) CI config shall be stupid simple. If you have more than like two lines in a script section, it goes into a Tools/Build script file that must work locally and is just called in a one-line CI script.

#1 guarantees you can operate without CI, and #2 guarantees you can move CI providers trivially.