Measure their productivity and they vehemently deny it and will sick lawyers on you. In the land of free speech.
The US is run by people with mafia mentality.
21 karma · joined September 18, 2023
Measure their productivity and they vehemently deny it and will sick lawyers on you. In the land of free speech.
The US is run by people with mafia mentality.
They died before hardware achieved their decades old visions. Not much of this work is net new description, moreso normalizing old descriptions with observation now that we can actually build the old ideas.
There are thousands of forums that require sign up just to read posts. Always has been.
Imagine being on a sinking ship and the captain is all; don’t worry, if we tie this life jacket to the handrail, it’ll stop the descent by floating on top of the water.
IT has been taken over by the rent seeking industrial complex. Peddling hallucination to prop up book sales and conference travel.
I have no doubt California businesses will immediately ship data outside California and play dumb.
Japan of today is nothing like Japan of 100 years ago.
Every nation has already faded away multiple times.
Looked at the TF code; my solution implements similar functionality to handle AWS CRUD ops. What I avoid is all the DSL parsing and such.
For me an AWS account is a struct with fields of AWS SDK resource types, which it seems is what TF resources map to (they handle a lot more so there’s more to it, but kind of sort of if I squint just right). Either going to duplicate the internal logic or DSL chunks per project, would rather avoid the context switch between syntax, “learning the TF ecosystem”.
Thanks again, though.
I’m sure there’s some 100% subjective, hallucinated value statement but never felt a reason to bother.
I’ve only ever used an AWS SDK and “saved state” to git in the form of my SDK scripts.
Switched from Python+boto to Go+SDK a few years ago rather than learn some DSL the Lindy effect clock was ticking on.