Being able to learn these things on your own is exactly what a CS degree is supposed to teach. In my career, I've taught myself how to make complex CLIs. Then

Being able to learn these things on your own is exactly what a CS degree is supposed to teach. In my career, I've taught myself how to make complex CLIs. Then CGI-based web apps. Then Java desktop apps. Then MVC frameworks. Then JS frameworks. Etc. Ditto for changes in development and deployment processes. Ditto for changes in DB technology. etc. My employer rightfully expected that, for a six figure salary, I should be a professional who is able to keep up with best practices. That's why they pay me well. They let me attend conferences and I negotiate for some "experimentation" time whenever there's a big shift in the tech landscape, but it's not like I'm disappearing for months at a time every 5 years. That'd be insane. I'm not very old. Hell, I don't even work in web development. It's just one of those skills I need to keep fresh because it comes in handy every once in a while. The changes in my actual domain of expertise have been even larger and much more difficult to keep up with. Coding bootcamps are expensive -- they often cost on the order of a single year of college. If you're going to need to go through a few of them in your career just to keep up with a single skill set -- building UIs -- that's more of a baseline competence than a real specialty, why not front-load and just get a good-quality degree that prepares you to teach yourself the easy stuff? Double major while you're at it.