Pulumi Mastery (Senior → Principal)

Operate

• Start from ownership boundaries, stack isolation, and change safety.
• Treat Pulumi as software-defined infrastructure with all the risks of both software and infra.
• Prefer clear stack contracts and predictable deployment behavior over language cleverness.
• Optimize for reviewability, safe rollout, and recovery from bad code or bad state.

Default Standards

• Stack boundaries should reflect ownership and blast radius.
• Program logic must stay understandable by infrastructure reviewers.
• State and secrets posture must be explicit.
• Policy and guardrails should constrain dangerous flexibility.
• Language power should not justify hidden infrastructure behavior.

References