The only places I've worked at/for as of the last 2-3 years that don't heavily rely on managed services were an absolute disaster. A lot of "not invented here" syndrome. A lot of anti-patterns and janky hacks to make things work.
Currently working somewhere 100% locked in to AWS and I've never been happier.
No, I definitely ignore recruiters. Internal recruiters I may respond, but if you're some consultancy firm or recruiting firm I'll never work with you.
My skills are in demand. When I want a new job I'll reach out for it. It'll be there.
From what I've read it'd be more equivalent of the bull getting out, you hearing about it and going to look for the bull, then forcing the bull to inseminate all your cows knowing that your neighbor typically charges $10k per.
Yes. I work for John Deere ,but can't speak for the company.
The tractor and combines are sending real time crop data, it isn't hard for someone to look at that data and see across all farmers that yields are a bit different from what the market is predicting and make a large profit trading on that insider knowledge.
Those who work on that software and the admins of the database are registered with the SEC as not allowed to trade commodities. All that money they could make is directly out of our customers pockets and they wouldn't let us have that data if were were not protecting it.
It is a zero sum game. Farmers sit on one side of the trade and farmers the other. Thus the value of the data is exactly equal to the amount farmers lose by the traders having the data.
As a long time terraform user, I've been playing with a spare time project in Pulumi. TF and Pulumi share providers, but that's the extent of it.
My quick observations:
* It's nice to write TypeScript as the configuration language
* The provider documentation is poor and lacks the examples that terraform has, I find my self reading terraform documentation to understand how to configure Pulumi.
* You're constantly fighting with "async" vs "Input" vs "apply" when using a value, basic cases are handled in Pulumi but as soon as you want to do something complex you're toast. Maybe I just am doing it wrong, but that goes back to the lack of docs.
* How it handles dev/production/staging is just a little off from my expectations, not that terraform at it's core does this well either (why terragrunt exists).
Overall it's not bad, but it's not a silver bullet either to the typical problems. And suffers from a "small" community problem where you can't google solutions to problems with the same success.
Your understanding is wrong. The CRUD logic of some commonly used providers is based upon that in Terraform providers, but the TF engine is not used by Pulumi.
No you’re not the only one. The problem with Terraform “Scripting” is in a lot of cases it takes a loooong time to find out your “runtime” errors. These are typically fat fingered strings. I think something like AWS CDK, where you find these errors at compile, time is a better approach.
I wasn't aware of this and I'm glad to see they're doing it. But my guess is this is a relatively recent offering in response to the AWS version and the issues I was mentioning.
terraform really needs to be run in CI/CD pipe. Even without the backend initialized you can run terraform validate which will find things like undeclared variables and messed up count and foreach references.
