Skip to main content

System status

Memory 2.4 GB of 3.8 GB
Disk 98 GB of 116 GB

Over 80%: clear old logs and images before it fills.

Health
Every check passed
CPU load
0.42 on 2 cores
Signed in
12 online
Guests
48 online
Queue
3 waiting, 0 failed

Messages 3 unread

HR Team

4 members · 2 online

Today
Jessy Ellis

Next week we close the project. Any questions before we do?

You

That is excellent news.

Read

Tom Brennan

I have been through the features — cannot wait to demo them.

You

Haven't seen the build yet — looking now.

You

Checking the build now.

Delivered

Jessy is typing…

Jane Perez wants to join

1 day ago · Design Team

Notifications 3 new

  • Today
  • Priya Raman asked you to approve access to Northwind Trading

    Unread. · Members

    Nora O’Brien

    nora@northwind.example · Member

  • Sam Okafor attached a file to Q3 forecast

    Unread. · Finance

    q3-forecast.xlsx

    Spreadsheet · 248 KB

  • Three variants are below their reorder point

    Unread. · Inventory

    Restock before the weekend

    Due 16 August 2026

    Stock Urgent
  • Earlier
  • Your email address is verified

    · Security

  • Marta Kowalski mentioned you in Autumn drop

    · Marketing

  1. Home
  2. Posts
  3. How we cut our build from 40 minutes to 6

How we cut our build from 40 minutes to 6

Published Engineering Priya Raman · · 9 min read

Performance

The seven days since it went out

Best of the quarter

Views

41,200

Against 8,900 for the median post

Median read

4m 12s

Of an estimated nine-minute read

Newsletter sign-ups

318

0.8% of everyone who arrived

Most traffic from
Hacker News — 22,400 arrivals
Then
The newsletter — 7,100 · search — 4,800
Read on a phone
61% of sessions

Comments

—

All moderation

The bit about the test suite running twice is the whole post. We found the same thing last year and it was a stray watch flag in a config nobody had opened since 2022.

Speed up your CI with our tool, free trial at fastbuilds dot example, first month half price.

Would you publish the actual timings per stage? Six minutes is a headline; the shape of where the other thirty-four went is the useful part.

History

Eleven days from first draft to live

  1. Published

    Went out on the 09:00 slot, as scheduled.

    Scheduler

  2. Scheduled for 25 August

    Held for the Tuesday slot rather than going out beside the release note.

    Tomás Ferreira

  3. Review approved

    Second pass. The benchmark table was rebuilt from the raw runs.

    Tomás Ferreira

  4. Changes requested

    Two numbers in the table disagreed with the ones in the prose.

    Tomás Ferreira

  5. Sent for review

    2,300 words, cover chosen, slug set to /blog/faster-builds.

    Priya Raman

  6. Draft created

    From the retrospective note on the build working group.

    Priya Raman

Details

Status
Published
Address
example.com/blog/faster-builds
Category
Engineering
Author
Priya Raman
Published
Last edited
Length
2,300 words · 9 min read

Cover

Shown at 16:9 in the feed and cropped square in the newsletter. Replace it in the editor.

What search sees

example.com › blog › faster-builds

How we cut our build from 40 minutes to 6

Six weeks of profiling, one cache that was never warm, and a test suite that had been running twice.

Dashboard Orders Products Customers Account Settings

Keyboard shortcuts