That might have been the promise but never the real value. As you say in practice the engineer needs to know ops & terraform along side their language of choice.
The real value of cdktf was more dynamic infrastructure provisioning while still having the plan / apply pattern.
Probably. GPT3.5 was really good at writing unit tests. I asked it to unit tests for some typescript code using jest and aws-sdk-mock. It did it as I would do. I really couldn't fault it.
Energy is life. But we've had commercial nuclear for over half a century. We as a society just chose to pollute instead of dealing with the real / not real risks associated with nuclear.
IMO Netflix and Amazon Prime's problem is they don't surface their good content enough. They mix it with their shitty content. They should make it stand out. HBO are good at this. When they make something good, that they know is good, they will rub your face in it with large high quality images.
I don't have time to shift out the good from the bad with Netflix.
Basically a controlled thermo nuclear reaction blasting out the back.
"One design would generate 13 meganewtons of thrust at 66 km/s exhaust velocity (or 6,730 seconds ISP compared to ~4.5 km/s (450 s ISP) exhaust velocity for the best chemical rockets of today)."
You certainly wouldn't want to use this to take off from Earth. But we could use it for deep space travel.
As much a fan of Terraform I am. If you didn't started defining your repos in Terraform from day 0, importing hundreds of repos, members, permission sets would be quite a lot more work than running this audit tool.
You're jumping to conclusions in your final statement there. The existence of inexcusable bad practices does not mean we should not try to mitigate against them, and I didn't say we shouldn't.
That's certainly a good idea. But the secrets shouldn't be in the codebase to begin with, certainly not production secrets. Production secrets should stay in production and no one has access. Whatever intends to use the production secrets should have first been developed in a dev environment and released to prod.
Doctors used to not wash their hands too. I get it though, and i've seen the same thing. Really it comes down to education and not granting access to secrets to people who aren't capable of handling them.
I'm not going to disagree with that and I'm not opposed to the privacy controls in GDPR. The context here in a solo dev who is dealing with GDPR. When you're trying to get a business off the ground, iterating fast and trying to build a business that can survive to day 2, every single bit of busy work should be avoided. Why reduce your chances of success by chasing a market that takes more work than other markets? The global market without Europe is big enough to support any startup; so long as you build something people want.
Those three are not all equal. "Production keys in source control" is the equivalent of a surgeon not washing their hands between between surgeries. It's basic level of professional competency that should not be violated. The latter two are bad mistakes, which shouldn't happen but do.
Australia has had a lot of asset inflation and is only recently starting to show in the consumer prices. eg afaik house prices are not included in the CPI
If I was starting a startup today. I'd probably just block Europe and focus on other markets initially. Loop back on Europe once you have product market fit and the resources to deal with GDPR.
The real value of cdktf was more dynamic infrastructure provisioning while still having the plan / apply pattern.