• 2 Surprising Truths About the Iron Triangle
• 3 Commandments of Performance Optimization
• 3 Reasons to Prefer References Over Pointers
• 6.0 Syndrome
• 6 Strategies to Simplify Software
• A Better Way to Put Data in Code
• A Comedy of Carelessness
• A Grumble About Buckets
• A More Important Manifesto
• A Quibble with Martin’s Optimize Later Notion
• Add Some More Extra Redundancy Again
• Adios to Computer Programming
• All I Really Need to Know I Didn’t Learn in Compugarten
• Annotating the Web
• Architects: Manage Risk Like a Vegas Bookie
• Are You Losing Enough Battles?
• Baby Steps
• Big Crud Isn’t Big Data
• Big Data in Motion
• Book Review: Poke the Box
• Book Review: Universal Principles of Design
• Bridging the Lacuna Humana
• Code Isn’t Art
• Coding Standards
• Comments on Comments
• Convoys As a Model For Distributed Architectures
• Coping with Organizational Alzheimers
• Courage Counts
• Decoupling Interfaces As Versions Evolve, Part 1
• Decoupling Interfaces As Versions Evolve, Part 2
• Decoupling Interfaces As Versions Evolve, Part 3
• Designing an Apex Predator
• Do Androids Browse For Electric Sheep?
• Don Kleinschnitz: Put a Stake In the Ground
• Don’t Forget the Circuit Breakers
• Earned Pragmatism
• Encapsulation Isn’t Just For Code
• Evolving Software Politics
• Example RPCD Interaction
• Exploring the Power of Deixis
• Farewell to Google Reader
• Features Are Not Chunks of Code
• Flexibility Is No Virtue
• George and the Flood
• Good Code Is Balanced
• Good Code Is Named Right
• Good Code Is Optimized
• Good Code Plans For Problems
• Good Fences Make Good Neighbors
• Grumpy Old Men, Opacity, and Optimizers
• Hair Raising Words
• Headers, Babies, and Bathwater
• High-Value Questions
• How Enums Spread Disease and How to Cure It
• How Software Is Like Biology
• How Sutter’s Wrong About Const in CPP 11
• How to Make a Const Correct Codebase in 4300 Easy Steps
• How to Point in Code
• Humility
• In Which Warnings Evolve Wings
• Interrupting My Interruptions
• Introducing Marks
• Julie Jones: Learn Voraciously
• Ken Ebert: Kill Three Birds
• Know Your Limits
• Lacunas Everywhere
• Learned Helplessness, Rats, and People Power
• Long Term Benefits of RPCD
• Lynn Bendixsen: Listen
• Manifestos
• Measurements, Plumb Lines, and System Thinking
• Mountains, Molehills, and Markedness
• My Bibifi Adventure
• My First Software-Defined Supercompute Cluster
• My First Tangle with the Tower of Babel
• On Bread Recipes, Maps, and Intentions
• On Forests and Trees
• On Pains and Brains
• On SEPs, Squirrels, and Meta Questions
• Paying Off Technical Debt
• Programmers: Learn How to Cloudify
• Programming Language Popularity Index
• Progressive Disclosure Everywhere
• Put Your Const Foot Forward
• Rockstars
• Roland Whatcott: Manage Momentum
• Role Models
• Role Play Centered Design
• Six Learning Tips For Tech Folks
• Small Files Are Your Friends
• Smart Geeks Think Like Cheerleaders
• Steve Jackson: Lead with Passion
• Steve Tolman: It Depends
• Taming Side Agreements
• Tech Debt, Leverage, and Grandmas Envelope
• The 8th Characteristic
• The Power of Simplicity
• The Scaling Fallacy
• The Third Half of Computational Economics
• Unencapsulate Yourself
• Use Kind Words
• Users Aren’t the Only People in Your Software
• Variadic Macros Tricks
• Weakened Dev Teams NIH
• What a Software Architect Is Not
• What Are Your Software’s Vital Signs?
• What Is a Software Architect?
• What Is Good Code?
• What Role Are You Playing in RPCD?
• What Should Be in Next C Compiler
• What Should Code Look Like When We Squint at It
• When Good Comments Mean Bad Language
• Why Cannibalism May Be Smart Business
• Why Exceptions Aren’t Enough
• Why I Don’t Blog About Great Code
• Why Mental Models Matter
• Why People Are Part of a Software Architecture
• Why Software Artisans Should Manage Their Influence
• Why We Need Try Finally, Not Just RAII
• Why You Should Be Proficient in a Tool Like Vim Or Emacs
• Why You Should Use an Ide Instead of Vim Or Emacs
• Why Your Software Should Cry
• Why