SYSTEM Cited by 1 source
Slack Quip¶
Quip is a collaborative-document product (Quip Inc., acquired by Salesforce in 2016; now a Slack-adjacent surface). At Slack, Quip's backend pipeline shares a build artifact pipeline with Slack Canvas — the two surfaces are delivered by the same Python-backend-plus-TypeScript-frontend stack.
Slack uses Quip as a primary example system in build-engineering retrospectives because its pipeline is "much, much more complex" than a canonical "Python backend + TypeScript frontend" application and exposes the interesting failure modes of large, intertwined builds (see sources/2025-11-06-slack-build-better-software-to-build-software-better).
Seen in¶
- sources/2025-11-06-slack-build-better-software-to-build-software-better — Quip's build pipeline is the subject of Slack's 60 min → 10 min build-speed-up case study. The original Quip+Canvas build had cycles, giant non-hermetic action nodes, and a Python↔TypeScript dependency edge that cost ~35 min/build on its own.
Related¶
- systems/slack-canvas — the shared-pipeline sibling surface.
- companies/slack — parent company.