A great essay from Jean Yang.
What I imply by developer expertise is the sum whole of how builders interface with their instruments, end-to-end, day-in and day-out. Certain, there’s extra focus than ever on how builders use and undertake instruments, and there are total talks and panels dedicated to the subject of so-called “DX” — but giant elements of developer expertise are nonetheless largely ignored. With builders spending lower than a 3rd of their time truly writing code, developer expertise contains all the opposite stuff: sustaining code, testing, safety points, addressing incidents, and extra. And lots of of those facets of developer expertise proceed getting ignored as a result of they’re advanced, they’re messy, they usually don’t have “silver bullet” options.
She makes the case that DX has maybe been typically oversimplified and there are classes of instruments which have very totally different DX:
My main revelation was that there are literally two classes of instruments — and subsequently, two totally different classes of developer expertise wants: abstraction instruments (which assume we code in a vacuum) and complexity-exploring instruments (which assume we work in advanced environments). Most developer expertise till now has been solely centered on the previous class of abstraction, the place there are extra simple methods to know good developer expertise than the previous.
Jogs my memory of how Shawn thinks:
It’s time we glance past the simple questions in developer expertise and begin addressing the uncomfortable ones.