A big problem these days is that you have to spend a week or even more getting your pipeline working. The problem domain should not be that difficult. There s

A big problem these days is that you have to spend a week or even more getting your pipeline working. The problem domain should not be that difficult. There should be a lot more automation and standards. It should be worth missing some customization or perhaps making the flow with the animation instead of everything being bespoke. You can probably write a faster or better suited for a project over using whatever library your programming language needs, most accept the trade offs with using the most generic ones. There is also ah explosion in the number of products used for each project. From projects I have been on lately that adds a hell of a lot of confusion and complexity for deployment and makes the solution overall Esp since most of the products have words and issues you need to be aware of. Last project they spent 3 weeks getting the pipeline going. For the last week and a half they brought in an expert in AWS to help them at a HUGE cost. Even he had tea trouble getting it working. We “had” to do this because “devOps” and save money buy not paying for “old fashioned not needed infrastructurepeole” The system were creating was not very difficult not would it ever need to scale much at all. . Cargo culting can be very harmfu.