Video Podcast is live.
Turn any doc, link, or idea into a two-host video show with studio scenes, multi-cam cuts, and B-roll. Ready in minutes.
Everyone else stops at audio. This is a show you can publish.
Try it: https://t.co/mwV67pFCDT
This is about as good as incident comms gets. Clear, honest, and apologetic, direct from the CEO. Committing to take corrective action, with dates no less. Exemplary!
Yesterday, WorkOS experienced a service disruption that caused elevated latency, timeouts, and authentication failures for many customers.
The incident was triggered by an unusual increase in session-creation traffic, but the root cause was ours: a latent transaction bug and insufficient workload isolation allowed non-critical analytics work to exhaust a shared database connection pool.
We fixed the defect, restored service, and are moving analytics out of the critical authentication path, adding stronger overload protection, and improving our ability to detect and contain failures faster.
Authentication infrastructure has to be dependable. We fell short of that standard and we’re sorry to our customers and their users who were affected.
Full postmortem: https://t.co/qqBzezIUdI
@zebriez Makers academy, a coding bootcamp. Generally, she helped students navigate rapid change. Literally, she taught meditation, yoga, introspection and feedback workshops.
@bcherny I often iterate on a plan 10+ times before starting work on it. First few iterations change a lot, later iterations change a little. Can we have an option to view a plan diff rather than the whole new plan to make this easier? I can imagine using both
@MattHdeJonge@traestephens@StevenLevy@MattHdeJonge hey, are you hiring software engineers?
> I’ve never seen such a categorical result in my career
This data point is impressive, never mind the anecdotes. Great to see openness to peer review as well.
Would love to meet. More on me: https://t.co/Skb8vLSNHj