Agree and understandable. No one puts YAML on their CV. You do put the overarching technology there though. Say, kubernetes. Configuring that can be a marketable skill.
Another place are CI/CD pipelines. Some jobs seem primarily about that, which I always thought extremely odd and boring. In that sense, the DevOps style of work is truly defeated (developers writing their own pipelines).
Thanks. I'm actually a data engineer but the org is removing Python and Scala from the picture while a data platform team develops a YAML-DAG solution and our team has been the experiment subject for the last 12 months.
I can't imagine being an engineer without writing a single line of code. I'm done.
And Yeah infra is being taken care by the other teams too. But the strange things is, whoever wrote the infra or YAML solution NEVER bothers to daily-manage them. We as the user have to fill in a lot of mundane stuffs. For example they never bother to get permissions for us, we have to do it by ourselves.
Anyway, they get the fun we get the shit. I'm getting out. I heard a lot of big corporations are like that, e.g. I watched the Netflix videos but they all make me shiver and unwanted to work as a DE UNLESS I'm in the platform/tool teams who develop those fancy things, otherwise I'm just a YAML monkey.
Another place are CI/CD pipelines. Some jobs seem primarily about that, which I always thought extremely odd and boring. In that sense, the DevOps style of work is truly defeated (developers writing their own pipelines).