Today's #RealWorldCode livestream, where we worked to remediate outage-inducing IO overload on a production database, left me surprisingly emotional.
So I'm gonna thread about inclusion, formal & informal dev education, and performance work.
Performance work is, hands-down, the single most impostor-syndrome-inducing area of development work I do. I'm pretty good at remediating perf issues within normal business applications, but it's hard to remember that.
Because of how perf work has traditionally been taught.
Performance work isn't formally taught. It's informally taught, through mentorship networks, often during or because of an incident. Effective performance work traditionally required deep knowledge of monitoring tools & a specific system's idiosyncracies. Hard to get from a book.
There's a thin line between telling folks that programming skill often matters less than team skills, product sense, & grit -- which is usually true --
and telling them programming skill *doesn't matter*, which is such a transparent lie that no one believes it.
We've created a world in which we try to tear down the false idol of "CS fundamentals" by asserting that team skills, product sense, and grit all matter more -- but that doesn't actually change people's minds about whether "CS fundamentals" == "programming skill."
We can say that "CS fundamentals" aren't the same as "programming skill" until we're blue in the face, but in order to actually convince folks... we need to define what programming skill *actually is.*
We have shied away from this because "programming skill" is hard to define.