Fight for the Human

Comprehension Debt emerges!

I expected to love Project Hail Mary (this was an easy prediction.

This month I gave two invited talks that as paired pieces form a kind of bracket to hold together several big things I've been thinking about and working on lately: community-based research for developer science and what it gets us (to an audience of rese…

My upcoming book, The Psychology of Software Teams, exists in the eyes of the International ISBN Agency, various book sellers, and most importantly my publisher: it's coming out July 14th!

The Sometimes-Wrong Bot When I was a postdoc, reflective of the inability of the university to contain my multitudes, I was cross-appointed in three disciplines (Cognitive Science, Computer Science & Engineering) in an interdisciplinary center (The Design…

You did your best, but it happened: somebody told you that you are the one who has to measure the ROI of AI on the developers in your software organization.

I decided to change my own mind about evolution in my freshman year of college, which is common: college is often the time and place where non-evolutionists grapple with whether we will become evolutionists.

I hosted another Developer Science Office Hour last month, and for some reason, decided I needed to blackmail myself into making it a brief (very brief!)

There's a paper I recently came across by Mohammad Tahaei and colleagues called Privacy Champions in Sofware Teams: Understanding Their Motivations, Strategies, and Challenges.

Technologists are pretty afraid right now that widespread usage of AI in software development (and more generally in our workplaces) is going to melt our brains.

Seven different people texted or otherwise messaged me about this study which claims to measure “the impact of early-2025 AI on experienced open-source developer productivity.”

So somebody came to you (maybe it was your own mind, that traitor!)

With some regularity, kind-hearted Technical people tell me that I Can Be Technical, Too.