This is a curated list of articles I've found thought provoking or informative. Organized by topics: Career Development, Coding/ Software Engineering, Data Engineering, Product/Project Management, Soft Skills, and Other.
Career Development
• Maybe you should do less 'work' by John Whiles
• How To Read Technical Books Effectively by Recep İnanç
• Being Glue by Tanya Reilly
• How to become a More Effective Engineer by Cindy Sridharan
• The Biggest Mistake I See Engineers Make by Zach Lloyd
• How to Mentor Software Engineers by David Golden
• How to Work Hard by Paul Graham
• Trapped in a Value Oasis by Will Larson
• Considering Size and Scope of Services by Bryan Landerman
• Model, Document and Share by Will Larson
• 25 Ways to Demonstrate Technical Leadership by Lee Mallabone
• The Engineer/Manager Pendulum by MipsyTipsy
• Michelle Bu's Story by StaffEng
Coding/ Software Engineering
• Command Line for Beginners by Germán Cocca
• The Act of Writing Code by Manning Publications
• What is Developer Experience? A Roundup of Links and Goodness by James Governor
• 23 Basic Principles in Software Architecture by Ali Zeynalli
• The APEROS Code Review Elements by Carlos Silvestre
• Hyrum's Law by Hyrum Wright
• The System Design Primer by Donne Martin
• Green Lumber Fallacy in Software Engineering by Chris Behan
• What's in a Good Error Message? by Gunnar Morling
• Importance of Building a Data Strategy for Business Growth by Kavika Roy
• A Hundred Things I Learned Working on the React Team by Dan Abramov
• Best Practices to Write Clean Python Code by Vani Gupta
• What is functional programming? A practical guide by Matthew Tyson
• The What, Why, and When of Single-Table Design with DynamoDB by Alex DeBrie
• I Test in Prod by Charity Majors
• The Debugging Mindset by Devon H. O'Dell
• What's awful about being a {software engineer, tech lead, manager}? by Brett Slatkin
• Yagni by Martin Fowler
• How to Write a Git Commit Message by CBEAMS
• Am I really a Developer or just a good Googler? by Scott Hanselman
• 5 Design Principles from a Software Architecture guru by Luca Pelosi
• Naming Smells by Peter Hilton
• The Rise of Worse is Better by Richard P. Gabriel
• Why I Write Dirty Code by Adam Tornhill
• The Collapse of Complex Software by Nolan Lawson
• A Unit Testing Practitioner's Guide to Everyday Mockito by Ivan Pavlov
• Technical Writing for Developers by Eluda
• How to Interrogate Unfamiliar Code by Isaac Lyman
• Best Practices for Code Review by SmartBear
• Code Review Best Practices by Michal Nowak
• Reflections on 10,000 Hours of DevOps by Matt Rickard
Data Engineering
• PostgreSQL at Scale: Database Schema Changes Without Downtime by James Coleman
• Data Quality Unit Tests in PySpark Using Great Expectations by Karen Bajador Valencia
• Scale Amazon Redshift to meet High Throughput Query Requirements by Erik Anderson and Rohit Bansal
• Run Big Data Applications without Managing Servers by Channy Yun
• Start Data Engineering Posts
• SQL Style Guide by Simon Holywell
Product/Project Management
• Agile Doesn’t Work without Psychological Safety by Timothy R. Clark
• Why you should Consider using Docs-as-Code by Nik Begley
• To Share the Work, Share the Decisions by Jessitron
• How Big Tech Runs Tech Projects and the Curious Absence of Scrum by Gergely Orosz
• Giving Project Teams More Autonomy Boosts Productivity and Customer Satisfaction by UT Austin
• Tech Debt is not a Burden, it's a Strategic Lever for Success by Matt Greenberg and Keya Patel
• Working with Product Managers: Advice from PMs by Gergely Orosz
• Great Engineering Teams Focus on Milestones instead of Projects by Jade Rubick
• Technical Debt by Martin Fowler
• Are your standups awesome? by Dave Smith
Soft Skills
• How to Ask Useful Questions by Josh Kaufman
• Putting Ideas into Words by Paul Graham
• Knowing when to say 'no' by Jon Parise
• Willingness to Look Stupid by Dan Luu
• The XY Problem by Unknown
• No Hello by Unknown
• People Spend Too Much Time On Decisions with Equally Satisfying Outcomes by Rob Henderson
• 11 Non-Technical Lessons for Software Engineers by Victor Pleșcan
• State the Problem by Leslie Lamport
Other
• Why is LinkedIn so cringe? by Trung Phan
• The Architecture Behind A One-Person Tech Startup by Anthony Simon
• Two Pizza Teams are just the Start Part 2 by Tom Godden
• Two Pizza Teams are just the Start Part 1 by Tom Godden
• Thorstein Veblen's Theory of the Leisure Class -- A Status Update by Rob Henderson
• In Praise of Memorization by Pearl Leff
• Experiment More, Fail Less by Phil Le-Brun
• Why Women Volunteer for Tasks That Don’t Lead to Promotions by Linda Babcock, Maria P. Recalde, and Lise Vesterlund
• Organic Startup Ideas by Paul Graham
• Maker's Schedule, Manager's Schedule by Paul Graham
• The Guerrilla Guide to Interviewing (version 3.0) by Joel Spolsky
• IBM's Asshole Test by John Public
• How Complex Systems Fail by Richard Cook
• Akin's Law of Spacecraft Design by Dave Akin
• Devs don’t want to do Ops by Scott Carey
• Google’s Heart framework: Choosing the Right Metrics for your Product by Zbignev Gecis