Bryan Helmkamp discusses insights from analyzing over 1T LoC daily, what makes a code metric valuable, when unmaintainable code may be preferable, and what prevents maintaining quality code over time.
Kriti Sharma talks about how Barclays is solving some of the toughest big data challenges in financial services using scalable, open source technology.
Dan North discusses a number of feedback models and techniques, where and how to apply them, explaining the sandwich feedback model, how it works and why it usually doesn’t.
Benjamin Wootton discusses doing DevOps in banking and financial institutions, providing advice on performing a DevOps transformation in such an environment.
Ryan Huber talks about some of the ways Slack approaches collecting, inspecting, and communicating security information to the security team and to the individuals in their organization.
Zane Lackey discusses adapting security to change, building security programs, lessons learned from bug bounty programs, running attack simulations and knowing when security has been breached.
John Willis breaks down what is known about Burnout. Willis takes a look at some survey data and tries to suggest ways to achieve healthier outcomes for ourselves and our colleagues.
Olaf Carlson-Wee explores micropayment and wealth storage use cases for bitcoin and examines cryptosystems used to facilitate micro-penny payments and secure $B in global bitcoin banks.
Peter Bourgon presents some of the idioms, design patterns, and practices that have proven themselves developing successful, scalable, and sustainable code using Go.
Ross Garrett explores how design decisions may be leading to poor UX, discussing the principles of reactive applications and how streaming APIs can deliver significant benefits over RESTful APIs.
Nik Wakelin discusses why developers dislike writing documentation, what can be done about it and how to improve the process of writing docs.