Skip to main content
Archive
-
Complexity Has To Live Somewhere
-
Work As Imagined
-
The ROI of a Solved Problem
-
Go And See
-
Rules For Drawing Cartoons
-
Acting Like an Operator
-
Ownership At Work
-
Opinions Held
-
Humans Acting At Scale
-
Placeholder for a Conversation
-
Psychological Safety
-
Managing Oneself
-
Up, Down. Both, And.
-
Loops, Loops, and More Loops
-
Engineering in the Time of Product Market Fit
-
Energy Levels
-
A Diagnosis Metaphor
-
Silos are Bad, Handoffs Fail, Async Is Hard
-
Two Beliefs About Organizational Constraints
-
Epistemological Models
-
If You Want To Get Something Done
-
Both Big & Small
-
Layers, Complexity, and Trends
-
Space Required
-
Choosing What Problem To Have
-
Modals Are The Worst
-
Choices: Engineering, Organizations, and Constraints
-
Front-End: Declarative vs Objective-Orientated
-
Reading Isn't Enough
-
Code As Communication
-
Engineering Speed is a Symptom
-
My Own (New) Management Reflections
-
What Is My Culture?
-
Ruffled Role Feathers, Why We Need Generalists
-
Product vs Engineering
-
MTTR is the Most Valuable Piece
-
Valuing Glue & Eyes Up
-
Kent Beck's Sigmoid Curve
-
How You Can See Me At My Best
-
The Value of Append-Only
-
Your Biggest Network Cost
-
More Mentoring
-
Remote: How it works for me
-
Not Everything Is Tech Debt
-
Against the Purists
-
What Building Software Feels Like
-
A Responsible Individual
-
Resilient Microservices
-
Finding Information Is Hard
-
Shared Understanding, Imperfect Representation
-
Progressive Delivery
-
Technical Debt Will Not Kill You
-
Now, imagine other people are different from you
-
Reading Code Is Hard
-
MVP means lots of different things.
-
Lots of $%&#! Agile
-
Why Donβt Engineers Write?
-
A 57 Million Dollar Story
-
Signposts on the Road
-
Valuing Things That Break
-
Valuing Outside Perspective
-
Valuing Understanding
-
Valuing Meetings
-
Observability: a goal
-
RDBMS + ORMs are too good. It is a problem.
-
Fun with the Event Loop
-
Many Hammers, Many Nails
-
Reflections On a Decade In Consulting