or subscribe with
Join 14,000+ readers for one email each week.
Digests » 281
The O'Reilly Velocity Conference is heading to New York City in just a couple of weeks and where will you be? At the office, wishing you weren’t missing the leading conference on DevOps, performance, cloud infrastructure, and more? With Pavilion Plus passes starting at only $149, you can't afford to miss it. Plus, as a Programming Digest reader, you can get 20% off of your Gold, Silver, or Bronze pass with code PDIG20—that’s up to $519 in savings! Find the pass that's right for you and start making your plans today.
this week's favorite
From the very start, we made very conscious engineering and product decisions to keep Discord well suited for voice chat while playing your favorite game with your friends. These decisions enabled us to massively scale our operation with a small team and limited resources.
The Reddit engineering team recently introduced Go into their stack to write a new ad-serving system to replace a third party system. Deval Shah talks us through the architecture of the new service, the Reddit team's experience using Go for the first time, and all the lessons they've learned from using Go to build this ad server.
I have a gripe with the phrase "systems programming." To me, it always seemed to unnecessarily combine two ideas: low-level programming (dealing with implementation details of the machine) and systems design (creating and managing a complex set of interoperating components). Why is that the case? How long has this been true? And what could we gain from redefining the idea of systems?
Reading someone else's code can be quite confusing. Hours can go on issues that should have been fixed in minutes. In this article, I would like to share some advice on how to write code that will be easier to understand and maintain.