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.
This week: Code quality for mobile apps, what’s wrong with your PR process, and whether public computers are rife with malware (spoiler: probably).
This week: The app that helps you fight for your data privacy rights, the right way to think about p-values, and old-school JavaScript.
This week: Chatting with the guy responsible for building the Call of Duty game engine, focusing the James Webb Space Telescope, and implementing a technical solution to help with amnesia.
This week: Data ownership in the AI world, 100 ways to visualize the same dataset, and how old is too old for Narnia.
This week: How one of the creators of React is rethinking IDEs for the AI era, what to do about a client who keeps changing the password to the website you’re trying to build, and how linear programming can identify money laundering.
This week: Why documentation is vital software infrastructure, making it easier for subject matter experts to contribute to your knowledge base, and tips for safely walking a dog while riding a bicycle (hint: maybe don’t).
This week: What launching rockets teaches you about hardware observability, why Jupiter spins so fast, and what you learn by interviewing 100 DevTools founders.
This week: Training autonomous vehicles, the science behind frozen seawater, and disappearing domains.
This week: AI-native development, self-driving cars, and how to improve your developer portfolio.
This week: The mystery of masked self-attention, the thirst of an AI company, and the superpower of simplicity.
This week: Taking a look at the tech stack that powers multimodal AI, the first rule of machine learning, and whether it’s possible to build a world without sound.
This week: Why generating tests is a good use case for AI coding tools, how to tell your manager that you might retire early if you don’t get a raise, and why your company needs junior devs.
This week: The safest way to store a password in a database, the cost of coding first and asking questions later, and what happens when you touch an AM radio tower with a pickle.
This week: Making LLMs’ default architecture more effective, identifying a mystery pipe, and one of the largest technical migrations in history.
This week: Decoding the decoder-only transformer architecture, why external contractors probably shouldn’t manage internal teams, and speeding up your webpage before it even loads.
This week: Navigating with Norris numbers, how to handle a difficult interview situation, and why Nintendo won the video game graphics war without trying.
This week: Improving a 40-year-old developer tool, how candid to be when leaving a team, and a legal framework for regulating AI.
This week: Developer experience beyond the spreadsheet, what to do when your coworkers are Big Brothering you, and why the creator of jQuery uses React and Typescript.
This week: The results of our 2024 Developer Survey are in; what makes Agile more, well, agile; and a guide to building complex Chrome extensions.
This week: The framework helping developers build AI apps, how compilers recognize complex patterns, and the oldest known recording of a human voice.
This week: How data are reshaping society, whether infinity is a real number, and why “wifi” is so hard to spell.
This week: Dealing with code review anxiety, the ethics of multitasking while working remotely, and the math of card shuffling.
This week: A framework for understanding generative language models, best practices for loaning money to a friend, and useful but overlooked developer skills.
This week: The real 10x developer, outlawing password managers at work, and fixing the two-page login.