Skip to content

Comment on Rethinking Infrastructure as Code from Scratchparent

Comments

With great power comes great responsibility.

And in an environment where staff are a cost optimization and not everyone is a 10x coder or engineer, there will be individuals in power who are not as responsible as you would like.

So it's better to have a system where you limit one individual's ability to cause harm rather than amplify it.

Automated validation has always seemed to catch that sort of risk just fine.

In an environment where staff are a cost optimization, tech debt and things like CI/CD are luxuries. Much of it will be half baked or poorly implemented. Automation of unit tests and validation are going to be afterthoughts at best.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.