This paper from Zhu and Godfrey looks at single-statement bug fixes in Java code: more specifically, at the differences between how bug are fixed by the people who created them and how they are fixed by other people. The authors found that people fix their own bugs more quickly than other people's, which falls under…
Operating what you build, empowered with amazing developer tools
Today, our cofounder and CEO Drew Houston shared the difficult news that we’ll be making reductions to our global workforce. Here is the full text of his email to Dropbox employees:
(With apologies to Derek Zoolander and Justin Steven. And to whoever had to touch the HP-UX NTP setup at Queensland Police after I...
There are many books available that deal with modernising legacy codebases. These books generally focus on how to go about understanding the legacy system, improving test coverage, introducing build automation, as well as strategies for refactoring or rearchitecting the codebase. However, Marianne Bellotti’s Kill It…
An open letter from a former Facebook and VMware engineering executive on how startups can best structure their release processes.
There's a lot to consider when charting the rise and fall of developer salaries over the years. Let's dive in!
In this article, Vlad shares his experience using the Apple M1 as a cloud engineer. He discusses the compatibility of various software, including D...
Excerpt from a speech Adm. Hyman Rickover (1900-1986) gave at Columbia University in 1982 outlining his leadership style.
SRE SLO book to understand service level objective meaning and the various service level terminilogy including sla slo sli to improve service reliability.
Blameless postmortems in SRE culture. Incident study that focus on root cause analysis and preventive actions, for culture of continuous improvement.
