2 ms·
You might consider it basic. I would have, insofar as I considered it pretty obvious even when I hadn't written a line of frontend code in five years, and webpa
by eropple 10y ago
You might consider it basic. I would have, insofar as I considered it pretty obvious even when I hadn't written a line of frontend code in five years, and webpack etc. weren't even on my radar then. ;) But my experience has led me to believe that it's not.
I think that's kind of the point of devops, though, is that something like a build system is a cross-cutting concern, that architectural decisions for an application need to involve people across the stack. Classifying somebody as "a sysadmin" is the problem in the first place, which is why I caveated my post as heavily as I did. My experience is that your "devops" or "sysadmin" people functionally become the "junk drawer programmer" who are relied upon for all sorts of weird stuff. I've been at jobs (and at clients) where I had to teach senior backend devs how to use VisualVM or what the implications of using Kafka and CQRS are. I've been at gigs like the aforementioned where I had to explain the ramifications of webpack to people knowledgeable and capable enough to make React dance. And so my definition is probably necessarily more broad...but it's also stuff I've had to do in practice, so, enh.
And, 'cause fair is fair, I think a "sysadmin" who couldn't step in and write production-quality code (allowing for a little ramp-up) is probably an endangered species over the next ten years, too.