I wonder if someone has written about IaC as (further) alienating programmers from any whiff of people who do physical labour (like racking servers). Or for that matter, the idea that there are people who do valuable work that is not programming.
(Then of course the IaC people got demoted to 'devops', not 'real programmers', because this is the way of the tech industry.)
@cks My first two years as a TD were spent doing IaC, as a person who had just spent four years racking servers - I filled an important niche in the team in actual fact but felt pretty incompetent the whole time.
I have "hot take" level opinions more generally about "User Friendlly" and how that all worked out. This is part of the set.
Chris Siebenmann
in reply to mhoye • • •I wonder if someone has written about IaC as (further) alienating programmers from any whiff of people who do physical labour (like racking servers). Or for that matter, the idea that there are people who do valuable work that is not programming.
(Then of course the IaC people got demoted to 'devops', not 'real programmers', because this is the way of the tech industry.)
JimmyChezPants
in reply to Chris Siebenmann • • •@cks
My first two years as a TD were spent doing IaC, as a person who had just spent four years racking servers - I filled an important niche in the team in actual fact but felt pretty incompetent the whole time.
I have "hot take" level opinions more generally about "User Friendlly" and how that all worked out. This is part of the set.
silverwizard
in reply to mhoye • •@mhoye I once met a system where they enforced DRY on all the code
Meaning we had a meta makefile which used make to run terragrunt to run terraform to build 40 AWS accounts with 40 separate unrelated configs