1
Let me give you some context. I work in the pipeline automation department of a company. Last month, our team decided to deprecate an internal tool due to several maintenance issues. So we created a pipeline that automates the implementation of this legacy tool, in case other teams needed to use it. (WHAT???)
This month, a guy in my team found some improvement scenarios in the automation. So I was chosen to implement this changes in this legacy internal tool.
The thing is, after I finished the adjustments, my pull requests are not getting approved due to adjustments meticulously requested by this guy in my team. Adjustments to make the pipeline automation even more resilient in complete unlikely scenarios.
But this same week, my TL sent notices to all the other teams informing them that this internal tool has been deprecated and they should no longer use it. So what sense does it make to have a pipeline automation that implements the use of the deprecated tool? And if it has been deprecated, why would I need to make an adjustment for the automation to be even resilient if no one should be able to use it anymore? So why am I being allocated to work on in such waste of time like it? (WTF???)
This makes me wonder, how many people have to work on something that they see no sense in doing at all.
So once again, if you're feeling useless, remember that I exist.
In my view, a great alternative would be the use of workflow tools, which have a graphical pipeline where teams can follow each step of the process along with its respective input and output, in a visual interface.
I see this type of design as an evolution of how software is developed, but I don't see a wide adoption by companies/startups when they are starting to develop their applications. What I see is the same old recipe being repeated infinitely, new project = microservices + cloud.
Note: to give examples of such tools, I will mention two that I found on the awesome-workflow-engines list on GitHub. - Apache Airflow - temporal(dot)io