What people recommend, in their own words, with the receipt.
Issue-tracking and product development tool for software teams.
8 things
TerraformSoftware
While we could have continued doing this, moving to infrastructure as code (in our case, Terraform) made spinning up a second region a lot easier.
Linear on moving its Google Cloud infrastructure to Terraform for multi-region
linear.app ↗·2024-05-23Wrong?
Cloudflare WorkersService Cloudflare
Since we already use Cloudflare Workers extensively, it was an easy decision to also use Cloudflare Workers for the proxy that routes requests.
Linear on using Cloudflare Workers as its multi-region request proxy
linear.app ↗·2024-05-23Wrong?
StyleXSoftware
StyleX by Meta gave us a better balance.
Linear on migrating its React apps from styled-components to StyleX
linear.app ↗·2026-08-26Wrong?
turbopufferSoftware
We built a new read path with turbopuffer to keep that query fast and predictable, even as our biggest workspaces continue to grow.
Linear on moving its delta sync read path from Postgres to turbopuffer
linear.app ↗·2026-08-18Wrong?
Google CloudService
Initially, Linear’s infrastructure was concentrated in a single location - Google Cloud’s us-east1.
Linear on where its infrastructure was originally hosted
linear.app ↗·2024-05-23Wrong?
RedisSoftware
The sync service uses a cursor to get changes not yet sent to clients and caches this cursor in Redis.
Linear's incident post-mortem describing its sync service
linear.app ↗·2024-01-30Wrong?
GitHub ActionsService
Moving our workloads off GitHub Actions to third-party runners with faster CPUs, higher-performance storage, and better cache infrastructure gave us faster machines to run the same pipeline on.
Linear on moving CI workloads off GitHub Actions runners to third-party runners
linear.app ↗·2026-09-21Wrong?
styled-componentsSoftware
styled-components served Linear surprisingly well for a long time.
Linear on why it moved off styled-components after it served well for years
linear.app ↗·2026-08-26Wrong?
Every entry is a verbatim quote and a link to the public post it came from. Nothing is paraphrased. If it is not on record somewhere public, it is not here.
The verdict is what they actually said: loved and liked are explicit; recommended means they told others to get it; uses means they only say they use it; read is a book on their public shelf with no verdict; mixed and disliked are kept too.
A dashed affiliate link, sponsored or their own label means the post disclosed a relationship. It is shown, never hidden.
The small bar beside a date shows how dated a recommendation is for its kind of thing.
The bar shows how dated a recommendation is, for its kind of thing. Full and green is recent. It drains, and turns amber and then grey, as the post gets older.
What counts as old depends on the thing. A laptop praised four years ago has been replaced twice; a book loved twenty years ago is probably still loved. The bar is empty after about:
A striped bar means the post carries no date and the date shown is an estimate. No date at all, no bar.