podcast February 5, 2021

Podcast 310: Fix-Server, and other useful command line utilities

Bottlenecks tend to emerge where you least expect them.
Avatar for Ben Popper
Director of Content

On today’s episode we talk about Slack’s exploration of its recent outage, our first impressions of Clubhouse, and ideas for keeping Stack Overflow questions from becoming outdated.

EPISODE NOTES

Check out the great post from Laura Nolan, a senior engineer at Slack, breaking down their outage. Paul wants some simple command line utilities for “fix-server” and “boot-it-all-up.”

Clubhouse was known early on for being popular with Silicon Valley, but it’s increasingly becoming a global phenomenon. You don’t have to wait for it to go public to invest,  you can buy shares right now in Agora, the Chinese company powering its real time audio chat.

Got ideas for how we can version Q&A on Stack Overflow to ensure questions with accepted answers don’t become outdated or obsolete? We’re planning to work on this problem, so send suggestions our way.

This week’s Lifeboat badge winner is Quinn, who answered the question: How to replace a string in a file using regular expressions?

TRANSCRIPT

Tags:

Related

newsletter February 12, 2021

The Overflow #60: Sequencing DNA with a USB dongle and open source

Welcome to ISSUE #60 of the Overflow! This newsletter is by developers, for developers, written and curated by the Stack Overflow team and Cassidy Williams at Netlify. This week, open sourcing DNA sequencers, Clubhouse, and finding the Nth prime number. From the blog Learn to program BASIC with a Twitter bot stackoverflow.blogTurns out you can do a lot in…
newsletter September 4, 2020

The Overflow #37: Bloatware, memory hog, or monolith

September 2020 Welcome to ISSUE #37 of the Overflow! This newsletter is by developers, for developers, written and curated by the Stack Overflow team and Cassidy Williams at Netlify. Thrill to the veteran Stack Overflow engineer who walks like a noob! Gasp at the 2000-year-old temperature reading! Marvel at the GitHub README that writes itself!…