In this second part of the series, I’ll describe the rhetorical situation using a framework used in college composition classrooms.

To succeed in software engineering, mastering code as a language is crucial, and "speaking code" is as important as writing and reading it.

“Simplifying” our language use can make our meanings less precise, and rob our audiences of the opportunity to deepen their own literacy.

AI Skill Threat is real. Software practitioners are afraid, anxious, and worried about the relevancy of their current skill sets.

Absent an invitation, even the most theoretically sound workshop, course, academy - what have you - will fail to garner learner engagement.

Our failure to communicate effectively in the engineering domain can have consequences inimical to our ultimate goal of shipping software.

When we think about coding – especially early in our journeys as code learners – we typically think about writing code.

Software development teams traditionally use the retrospective ceremony to reflect on their results, performance and processes. But the...

The overarching objective was to arm folks across the company with the knowledge to diagnose the accessibility of our products.

I’ve never been able to sustain the motivation to actually complete a MOOC. Until now!