The cost of keeping up
Service workers, Houdini, shadow DOM, web components, HTTP2, CSS grid, "micro-front ends," AVIF — and that list stops short of JavaScript frameworks and libraries. None of it was especially new in 2020, yet taken together it works like a clapperboard, cueing the familiar reflex of fear of missing out or imposter syndrome. How does anyone stay current, let alone learn something new?
Melanie Sumner put the tension plainly: "Anyone else feel like paying attention to any specific area of development causes the other skills to rust?"
Genuine depth requires seclusion — a single focused path that etches only a tiny arc on the complete circle that is the web. Mastery delivers both the elation of achievement and an awareness of everything untraveled, much as Matt Might's The Illustrated Guide to a Ph.D. shows. Expanding the boundaries of your own sphere of knowledge is exhilarating, but it resembles reaching a remote mountain peak only to see more summits to the horizon. It is a solitary place, not without reward, and not easily replicated: the next trek starts from the bottom again.
A pandemic of isolation
The seclusion is as physical as it is mental. Meetups are gone, along with the watercooler moments and the overheard new thing. Asking for help was hard enough when you could tap someone on the shoulder and interrupt their flow; it feels stranger still to strike up a call or chat when stuck. Everyone is at once a click and a mountain away.
Sharing out early
Where I once took heads-down days to research a problem, I now try to share findings in nearer-to-real-time. The feedback loop tightens, and I have adjusted the internal clock that warns me I have spent too long on the problem. The team exists to help one another, so we set aside time to pair program, mob, and demo. The plans have setbacks:
https://twitter.com/bmuenzenmeyer/status/1336068265852989441?ref_src=twsrc%5Etfw
There was also the bug that consumed four hours, until fresh eyes glanced at the stack trace and found a new path in fifteen seconds.
Combined arcs, shared context
Working this way unites skillsets: combining the arcs of knowledge across the tech the team needs unblocks each of us faster, like long-haul truckers tag-teaming a journey. Shared understanding helps us retain context and communicate with less writing, and closer work on even mundane tasks has changed things. Take the engineer who offers regex tips every time. Where I once bristled, or simply leaned on their experience, I now get ahead of the task: "I don't know how to do that" turns into better and better ideas about where to take a first step. That is a teensy bit more circumference to my skillset, a bit more of a climb up a new mountain, with a guide who shows me the trailhead.
I still walk alone sometimes, and some of my best work happens there. But I now have a better sense of what I don't know, and a working realization that the team can go further together than any one of us. I fret less about the peaks I haven't explored, and I ask others about what lies over there more readily than ever.



