The Overflow #118: What makes developers happy at work?
This week: what makes developers happy at work, how sharding a database can make it faster, and whether it’s a good idea to intentionally insert bugs into your code.
The Overflow
A newsletter by developers, for developers, curated by Cassidy Williams and the Stack Overflow team. Every week, we’ll share a collection of great questions from our community, news and articles from our blog, and awesome links from around the web.
The Overflow #117: New podcast hosts, the CEO on PagerDuty, and horrible code on a deadline
This week: our new crew of podcast hosts, the CEO who still takes his turn on PagerDuty, and the existential horror of working with abysmal code when a deadline looms.
The Overflow #116: Stop aggregating away the signal in your data
This week: how to stop aggregating away the signal in your data, the hipster programming paradigm, and the junior software engineer making all the architecture decisions at their startup (are they working hard enough?).
The Overflow #115: What engineering managers give up, an AI bot that can ace technical interviews, and a one-stop monorepo resource
Welcome to ISSUE #115 of The Overflow! This newsletter is by developers, for developers, written and curated by the Stack Overflow team and Cassidy Williams. This week: what you give up when you move into management, an AI bot that’s better than you at answering technical interview questions, and resources to help with monorepos and functional programming.
The Overflow #114: Work estimates that account for friction, continual learning, and the coders inspired by Tumblr
Welcome to ISSUE #114 of The Overflow! This newsletter is by developers, for developers, written and curated by the Stack Overflow team and Cassidy Williams. This week: realistic work estimates, creating a culture of continual learning, and how Tumblr inspired a generation of women to code.
The Overflow #113: Top-paying tech jobs
Welcome to ISSUE #113 of The Overflow! This newsletter is by developers, for developers, written and curated by the Stack Overflow team and Cassidy Williams. This week: tech’s top-paying jobs, building a killer company brand, going from C-suite to IC, and that one developer who’s always doing Leetcode puzzles at work.
The Overflow #112: Psychological safety for high-performing teams
Welcome to ISSUE #112 of The Overflow! This newsletter is by developers, for developers, written and curated by the Stack Overflow team and Cassidy Williams. This week: the importance of psychological safety, dynamic programming for beginners, and a ridiculous island where crypto-bulls can relax free from skeptics and naysayers.
The Overflow #111: Why securing code repos is a shared responsibility
Welcome to ISSUE #111 of The Overflow! This newsletter is by developers, for developers, written and curated by the Stack Overflow team and Cassidy Williams. This week: why securing your code repos is a shared responsibility, finding the flow state, and the discovery of nuclear energy.
The Overflow #110: The Log4j vulnerability by the numbers
Welcome to ISSUE #110 of The Overflow! This newsletter is by developers, for developers, written and curated by the Stack Overflow team and Cassidy Williams. This week: making hard decisions about optimizing software quality attributes, exploring whether running a random search 60 times is as good as a fancy algorithm, and the wrong way to learn…
The Overflow #109: Developers and the Great Resignation
Welcome to ISSUE #109 of The Overflow! This newsletter is by developers, for developers, written and curated by the Stack Overflow team and Cassidy Williams. This week: what the Great Resignation means for developers, the team helping underserved communities build their own LTE networks, and why Canon is telling customers how to defeat its DRM. From…
The Overflow #108: Determining dependencies and phantom braking
Welcome to ISSUE #108 of The Overflow! This newsletter is by developers, for developers, written and curated by the Stack Overflow team and Cassidy Williams. This week: UX headaches, the clear downsides of phantom braking, and testing with real dependencies instead of mockup or fakes. From the blog Favor real dependencies for unit testing stackoverflow.blogWhich dependencies should…