Stack Overflow Blog

July 27, 2020

Full data set for the 2020 Developer Survey now available!

We love to learn about what moves developers and technical workers. That’s why each year, we ask the tech community about their jobs, their tools, and their aspirations. We also love open source, so since 2011, we’ve made the raw data set available for you to explore! We’re happy to announce that this year’s raw…

Ben Popper Director of Content

code-for-a-living July 24, 2020

The perils of impersonation tooling

On Wednesday, July 15th, a bitcoin scam hit Twitter. Celebrities such as Elon Musk, Barack Obama, and Bill Gates appeared to tweet out a message that promised to return double the amount of bitcoin sent to a specific wallet. It wasn’t a spontaneous and simultaneous act of generosity, it was a scam. At this point,…

Ryan Donovan

newsletter July 24, 2020

The Overflow #31: Fresh data

July 2020 Welcome to ISSUE #31 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 chatting about diversity at Stack Overflow, wondering whether it’s wise to use your face as a password, and exploring the origin story of…

Ryan Donovan

the-loop July 23, 2020

The Loop: Our Community Roadmap for Q3 2020

This quarter, we tried something new for the Community Team roadmap and worked through every idea the community team had in an initial planning session. Here's what made the cut for Q3.

Sara Chipps Director of Product, Community

code-for-a-living July 20, 2020

Linters aren’t in your way. They’re on your side

Traditionally, linters make sure your code is clean and easy for teammates to read. They check for errors, bugs, style, and more. While they are more prevalent in dynamic/interpreted languages, they are not limited to them. Getting code as tidy as possible is the goal, but linters can also take some time getting used to, be a distraction, and might even be impossible to introduce to old, large code bases. We look at why they might still be worth your time.

Medi Madelen Gwosdz Content Strategist

newsletter July 17, 2020

The Overflow #30: Goodwill hunting

July 2020 Welcome to ISSUE #30 of the Overflow! This newsletter is by developers, for developers, written and curated by the Stack Overflow team and Cassidy Williams at Netlify. For your consideration, lessons learned from flunking code screenings, gas in a chips bag, and data getting to the bottom of the women’s tops on Goodwill.com.…

Ryan Donovan

community July 15, 2020

How the medical sciences exchange helped me with med school

As a 2nd year medical student, I was beginning an intense period of independent study for our first licensing exam (Step 1) when the COVID-19 pandemic hit in April. Studying for this test meant that I had less structured time for volunteering, so I wanted to find a way to contribute to the pandemic effort…

Dylan Tan

code-for-a-living July 13, 2020

Tales from documentation: Write for your clueless users

When you're documenting anything technical, it's easy to forget what it's like being ignorant of how the software works, especially if you built the thing.

Ryan Donovan

code-for-a-living July 8, 2020

Improving performance with SIMD intrinsics in three use cases

Many developers write software that’s performance sensitive. After all, that’s one of the major reasons why we still pick C or C++ language these days. When done right, supplementing C or C++ code with vector intrinsics is exceptionally good for performance.

Konstantin