Skip to content
NewSee how fast an edit goes live on this site
Halftone

Customers

How a university lab ships every day, part 2

What changed for the people doing the work every day.

How a universitylab ships everyday, part 2HALFTONE / JOURNAL
Gus Heller
Published 2 min read

The team publishes several times a day, often from a phone between meetings. Before switching, every change waited in a queue for an engineer. This post covers what we changed, why, and what it means for you.

#Rolling it out

Their editor-in-chief describes the old process as "a ticket and a prayer". Now a reporter fixes a typo and sees it live before they have closed the tab.

What surprised them most was the calm. Launch days used to involve a war room; now they schedule posts the week before and go to lunch.

#Where we started

Guest contributors get access to their own drafts and nothing else, which removed a whole category of permission requests from the inbox.

They started with a single project and expanded once the first launch went smoothly. Six months later, every team in the organization is on board.

#The constraint

Their advice to other teams is simple: measure the time from "done" to "live", and treat every minute of it as a bug.

The team publishes several times a day, often from a phone between meetings. Before switching, every change waited in a queue for an engineer.

Their editor-in-chief describes the old process as "a ticket and a prayer". Now a reporter fixes a typo and sees it live before they have closed the tab.

  • Run independent steps in parallel
  • Keep the previous version one click away
  • Cache what never changes

#Results

What surprised them most was the calm. Launch days used to involve a war room; now they schedule posts the week before and go to lunch.

Guest contributors get access to their own drafts and nothing else, which removed a whole category of permission requests from the inbox.

They started with a single project and expanded once the first launch went smoothly. Six months later, every team in the organization is on board.

“A cache key must include everything that can change the output, and nothing that cannot.”
Ada Rivers

#What changed

Their advice to other teams is simple: measure the time from "done" to "live", and treat every minute of it as a bug.

The team publishes several times a day, often from a phone between meetings. Before switching, every change waited in a queue for an engineer.

Their editor-in-chief describes the old process as "a ticket and a prayer". Now a reporter fixes a typo and sees it live before they have closed the tab.

“A cache key must include everything that can change the output, and nothing that cannot.”
Fen Alvarez
Inside a12-person studioHALFTONE / JOURNAL

Customers8 min

Inside a 12-person studio

What changed for the people doing the work every day.

Ivo Santos