HackSoftware
Hack makes our developers faster by improving productivity through better tooling.
Why Slack migrated its PHP codebase to Hack
2020-04-14·slack.engineering ↗
Recommendations you can check.
8 things
HackSoftware
Hack makes our developers faster by improving productivity through better tooling.
Why Slack migrated its PHP codebase to Hack
2020-04-14·slack.engineering ↗
HHVMSoftware
We stayed with HHVM because it offers an entirely new language
Why Slack stayed on HHVM
2020-04-14·slack.engineering ↗
quic-goSoftware
After careful consideration, they chose quic-go to serve as the foundation for the new functionality.
Slack on picking quic-go to add HTTP/3 probing to Prometheus Blackbox Exporter
2026-03-31·slack.engineering ↗
VitessSoftware
Vitess is the present and future of Datastores for Slack and continues to be a major success story for us.
Slack's migration from active-active MySQL clusters to Vitess
2020-12-01·slack.engineering ↗
KarpenterSoftware
Kubernetes worker fleets use Karpenter for lifecycle-driven updates.
Slack's Shipyard EC2 platform, on how Kubernetes worker fleets are updated
2026-07-14·slack.engineering ↗
SalesforceService
If it’s a sales lead, it gets piped to Salesforce where it’s assigned to a relevant sales rep from across the world (we’re global after all!).
Slack engineering on its marketing-site forms, which route sales leads into Salesforce (written before Salesforce bought Slack).
2020-09-15·slack.engineering ↗
ZendeskService
With the Contact Sales form, we go a step further and pipe the submission to Zendesk or Salesforce too, depending on the input we’ve received from the user.
Slack engineering on routing slack.com form submissions to Zendesk or Salesforce.
2020-09-15·slack.engineering ↗
OptimizelySoftware
Below is an experiment we ran in Optimizely (a leading progressive delivery & experimentation platform) to test if calling out required fields with asterisks will help with the conversion rate.
Slack's web team A/B tests marketing-site form conversion in Optimizely.
2020-09-15·slack.engineering ↗
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 shading behind a date shows how dated a recommendation is for its kind of thing.
The shading behind a date shows how dated a recommendation is, for its kind of thing. Fully green is recent. It drains a quarter at a time as the post gets older, and is empty once it reads as dated.
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 shading is gone after about:
Stripes mean the post carries no date and the date shown is an estimate. No date at all, no shading.