Regardless of how you fall in the Pulumi Vs Terraform preference scale, Pulumi is pretty damn simple and shouldn't take any time to get your infrastructure working in it.
I wouldn't agree with that. I was heavily working on a fairly straightforward infrastructure a year ago and encountered many issues in Pulumi either not supporting a feature or having to work around a bug in Pulumi. It worked, and it was nice when it did and a great DX, but when it fell apart it was quite a burden to figure out what to fix/workaround. Our infrastructure was lambda+CloudFront+S3 and a route based LB with RDS. Nothing crazy.
Yes, I'm sure the Pulumi team has updated to include those features (I can't remember what but if needed I can go find the infra code since the startup went kaput) and fix some of those bugs but they're a small dog chasing a racecar and may never catch up.
I think one of the virtues of Terraform is precisely being more limited than a full programming language. The temptation to add abstraction overhead can be too much for some teams.
Not necessarily. I know great programmers who don't really understand infrastructure. If you assign people who know the project and the language well but haven't been bitten by sysadmin/ops concerns they could make a mess of things thinking their common sense applies everywhere where they can write code.
take with a grain of salt, I only have minimal experience with both, but I really like the fact that pulumi is code over terraform config. Keeps me in the same toolchain, no need for extra plugins, etc.
Regardless of how you fall in the Pulumi Vs Terraform preference scale, Pulumi is pretty damn simple and shouldn't take any time to get your infrastructure working in it.