I was educated in a world that assumed IT ("Business Information Systems" in those days) people needed Assembly Language (and COBOL and FORTRAN). I entered a professional IT world chock full of Assembly programmers. For the decades I lived in that world, there were bunches of full-time, captive employees, writing Assembly Language. My main programming language was as far away from the assembler as it could be and stay on the same machine.
I have personally never NEEDED to code to the assembler, but I recognize cases when that need might exist. There are mathematically intensive sets of instructions that are best delivered in Assembly Language for the value of performance. Many (most?) high-level languages offer some keyword, e.g., ASM, by which to invoke the assembler. If you want to program games or high-performance video transformations, the assembler might be your friend.
I explored Intel x86 Assembly Language for a little while back in my C days. I wrote a program to read/write sectors at the level of the hard drive (ANY sector ANYWHERE on the hard drive) without mediation by a sane interface...scared my pants off to have that level of power.
So, yeah, I think coding to the assembler still has and likely always will have a place, a very specialized place but not one I care to inhabit and not one I would recommend to other programmers in general.
There's almost certainly more productive ways to spend your time while you're young.