Talk about your next project
Blacksmith executive brief

The lesson

Argue that your category is harder than it looks by breaking one everyday unit of work into its separate workloads and putting your own fleet numbers on each.

The move

The piece opens with a first-person hiring story: the author's past storage work at Google and Datadog, and why he came for 'that workload,' not 'managed CI.' Under 'What a CI job actually does, at scale' it walks a single ephemeral microVM through fetching the repo, environment setup, integration tests, incremental caching and persisting artifacts, with a diagram of each. 'Churn is the overarching challenge' then gives the fleet scale, about two petabytes a day written and about 95% discarded, and 'Scale is also concurrency on shared data' covers thousands of jobs reading one snapshot and many writing deltas to the same base.

Why it works

  • Our readOpening with why an experienced storage engineer chose this problem makes the technical claim feel earned before any architecture shows up.
  • Our readSplitting one CI job into named workloads gives the reader a model they can check against their own pipelines.
  • Our readClaim-style headings like 'Churn is the overarching challenge' let a skimmer follow the argument that standard storage was sized for data that accumulates.

What not to copy

Don't copy the personal career backstory or Blacksmith's microVM and petabyte figures. Keep the structure of a credible narrator, one unit of work broken into its parts, and headings that each state one reason the obvious tools fall short.

More from Blacksmith

More executive briefs

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.