Understanding something and optimizing it are not the same skill set. The author of the article seems to imply that even looking at a pipeline workflow is too d

Understanding something and optimizing it are not the same skill set. The author of the article seems to imply that even looking at a pipeline workflow is too daunting for developers, which is what I'm challenging. I personally am working on a horrendously slow pipeline right now, and I agree that it's frustrating to troubleshoot. But ignoring the problem is certainly not the solution - I've slowly but surely chipped away at various aspects and have a much better understanding of our CI/CD now. In the words of Jake the Dog, "Sucking at something is the first step to getting good at something."