Skip to content

Conversation

@asafashirov
Copy link
Contributor

@asafashirov asafashirov commented Oct 14, 2025

Add new case study for Wiz showcasing how they use Pulumi's Automation API to manage Kubernetes infrastructure at global scale.

Add new case study showcasing how Wiz uses Pulumi's Automation API to manage thousands of Kubernetes clusters across hundreds of data centers globally, processing hundreds of thousands of infrastructure updates daily.
@claude
Copy link
Contributor

claude bot commented Oct 14, 2025

Pull Request Review

I've reviewed this case study and found it to be well-written overall. However, there are several issues that need to be addressed before merging:

Critical Issues

1. Inconsistent title attribution (Line 17 vs Line 55) - The quote attribution lists Yarin Miran as Senior Software Engineer in the frontmatter, but the body text refers to him as Lead Engineer at Wiz. These need to be consistent.

2. Awkward phrasing (Line 51) - This infrastructure foundation became one of the factors in Wiz's position as one of the fastest-growing companies repeats one of the twice and feels redundant.

3. Heading case inconsistency (Line 77) - Millions of Resources, Tens of Thousands Kubernetes Clusters should be in sentence case per STYLE-GUIDE.md.

4. Em dash spacing (Lines 22, 49, 55) - Em dashes should not have spaces. Replace space-dash-space with em dash (no spaces).

5. Double spacing (Line 113) - thousands of Kubernetes clusters has two spaces.

6. Empty lines (Lines 115-116) - Remove one of the two empty lines before the final paragraph.

7. Verb tense (Line 91) - achieving FedRAMP High authorization in September 2025 should be past tense since today is October 2025.

8. Hyphenation (Line 109) - customer centric should be customer-hyphenated.

Style Issues

9. Marketing language - Avoid vague qualifiers like game-changing (Line 83) and meteoric (Line 109). The concrete metrics speak for themselves.

10. Comma splice (Line 81) - But the real story isn't just about the numbers, it's about operational efficiency needs an em dash or semicolon.

11. Section title mismatch - Line 69 heading doesn't match the frontmatter section label on Line 31.

12. Repetition - The exec_summary is nearly identical to the Executive Summary first paragraph. Consider differentiating them.

Summary

Strong case study with compelling metrics. Main issues: formatting inconsistencies, title attribution mismatch, and minor redundancy. Please address and resubmit for review.

@pulumi-bot
Copy link
Collaborator

@asafashirov asafashirov marked this pull request as draft October 14, 2025 16:56
@pulumi-bot
Copy link
Collaborator

adding missing part of exec summary
@pulumi-bot
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants