We explore the traits that have led to the rising popularity of the Go programming language.
Welcome to ISSUE #45 of the Overflow! This week: why the meaning of 60Hz depends on whether you are a monitor or a lightbulb, how the community team smashed 631 tickets in just two weeks, and why what we call CI/CD is actually only CI.
Our CEO looks back on his first 12 months at Stack Overflow and shares his thoughts on what we're planning for the future.
As many offices go fully remote, learning how to approach key meetings with your manager can pay big dividends.
You’ve gone through the motions and play-acted a disaster recovery scenario, but despite spending a lot on the production, it’s not real. What you have is a fairy tale: “Once upon a time, in theory, if everything works perfectly, we have a plan to survive the disasters we thought of in advance.” In practice, it’s more likely to be a nightmare.
Welcome to ISSUE #44 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, get in the fast lane and start pooling your database connections, make a CPU out of electronic components drawn by hand on paper, and learn to toggle multiple property…
We review our ticket smash event, lay out our roadmap for Q4, and talk about what we've been learning from our moderators.
When you already know your co-workers and how they approach work, that is fine as they probably haven’t changed all that much since the start of the pandemic. You cannot safely transfer those assumptions to new team members, however, as people remain people, rather than the microservices that they may seem over the internet.
Welcome to ISSUE #43 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, we’re coding for the long game, learning the difference between cats and not cats, and translating our favorite JRPGs into English. From the blog Play the long game when…
We tend to rely on caching solutions to improve database performance. Caching frequently-accessed queries in memory or via a database can optimize write/read performance and reduce network latency, especially for heavy-workload applications, such as gaming services and Q&A portals. But you can further improve performance by pooling users’ connections to a database. Client users need…