or subscribe with
Join 14,100+ readers for one email each week.
Digests » 274
The O'Reilly Velocity Conference will help you stay ahead of important trends in systems performance, cloud infrastructure, security, and more. You'll learn from experts and practitioners like Jaana Burcu Dogan (Google), Alice Goldfuss (GitHub), Stephanie Hurlburt (Binomial), and scores of others. Use code PDIG20 to save 20% on your Gold, Silver, or Bronze pass. That's a savings of up to $599 when you register during Early Price, now through August 17!
this week's favorite
Rockstar is a dynamically typed Turing-complete programming language. Rockstar is designed for creating computer programs that are also song lyrics, and is heavily influenced by the lyrical conventions of 1980s hard rock and power ballads.
Stop rearchitecting your code! The professional developer values stability over "code purity." Instead of pursuing a Shangra-La vision of code perfection with each and every release, just be nice and write stable APIs. In this post, I talk about taking practical steps toward writing code that remains stable over time.
There are many factors which can be a catalyst for bad software, from the tools being used, to the quality of communication inside your team, to the personal stake developers have in its success, to the testing methodology you use.
As a software engineer, I spend a lot of time reading and writing design documents. After having gone through hundreds of these docs, I’ve seen first hand a strong correlation between good design docs and the ultimate success of the project.
In June we focused our Test in Production Meetup around chaos engineering. Nora Jones, Senior Software Engineer at Netflix, kicked off the evening with a talk about how Netflix tests in production.