The author's final point is quite valid - to not become complacent about your expertise.
But the idea that expertise does not exist is flawed. I'm old enough to have been working online since before "the web", and while there are rapid changes in the specific toolkits, the core technology moves slower.
Sure, the hosting is now virtual not physical. SSL exists. Websockets exist. Javascript is its own beast now. The layers of caching and load balancing can be scary to us plain old developers. But the core HTTP request/response cycle, and the rendering and running of HTML and scripts has not had a fundamental paradigm change. DNS still drives end user connectivity, and the same old 7 layer network model still applies.
So yes, some things change, but don't throw the rest of it out just because you are picking up a new language or three. The picture is bigger than that.
Excellent comment, I fully agree with what you're saying. My intent was never to suggest "throwing out" previous knowledge but to instead recognize there's always more to learn and to keep building on that. Once you stop learning, the web quickly surpasses you.
I never stopped, and sometimes feel a little overwhelmed... I try to stay abreast of what's going on, even outside of what I'm working with. At least enough to have knowledge of what's on the horizon or in my peripheral...
That said, even with what I'm actively tracking, mostly JavaScript heavy web applications, Node/iojs, ES6/ES2015, ES7/ESNext, BabelJS, React, Riot, Mercury, Angular, etc.; It's a lot to keep up with. Everything gets to be pretty significant very quickly. That doesn't even include advances in .Net (ASP.Net/MVC, core-clr, etc), Java, Python, Go, the list goes on. It's impossible to know every tool. But it is possible to know and understand the concepts behind web applications, which aren't changing quite as quickly. I understand how SPDY/HTTP2/WebSockets and even bits of WebRTC work. If you understand how the pieces fit together, and how to bend them to your will...
If you understand how web applications work, you might be an expert.
If you aren't afraid to look at and consider new tools, you might be an expert.
If you know when to be pragmatic about your software design, you might be an expert.
If you don't loosely apply a software design pattern because it kind of fits, you might be an expert.
There's no absolute, it's just a matter of knowing more than most, and being able to apply it in practice.
But the idea that expertise does not exist is flawed. I'm old enough to have been working online since before "the web", and while there are rapid changes in the specific toolkits, the core technology moves slower.
Sure, the hosting is now virtual not physical. SSL exists. Websockets exist. Javascript is its own beast now. The layers of caching and load balancing can be scary to us plain old developers. But the core HTTP request/response cycle, and the rendering and running of HTML and scripts has not had a fundamental paradigm change. DNS still drives end user connectivity, and the same old 7 layer network model still applies.
So yes, some things change, but don't throw the rest of it out just because you are picking up a new language or three. The picture is bigger than that.