You don’t really need to become the best at it, but at least learn to read it.
And why should you do that?
Because every line of high-level code ends up as assembly. If you care about what your code actually does, you need to see the real thing.
There are tons of things that you will learn when learning assembly, what things? The following:
<ul>
<li>How memory really works (stack, heap, registers).</li>
<li>What function calls look like under the hood.</li>
<li>How compilers translate your logic into raw instructions.</li>
<li>Why some code is faster (or bloated).</li>
</ul>
How it can help you in other domains:
If you are someone who wants to go into reverse engineering, malware analysis, or low-level offensive security?
Assembly is your playground. You’ll be miles ahead of script kiddies.
But First…
Assembly has pre-reqs.
Know some C. Understand memory, call stacks, and pointers.
It’s not that beginner-friendly, but it can be, if you have a proper background.
Keep in mind:
Reading assembly won’t make you a better coder overnight.
But it’ll definitely help you in the long run.

Knowledge by Execution - Breaking Down Tech for the Mango Man (Aam Aadmi/Regular Person) - https://www.sknexus.org/

SK NEXUS

Learning to read assembly language can enhance your understanding of how high-level code translates into machine instructions. It provides insights into memory management, function calls, and compiler processes, which are essential for reverse engineering, malware analysis, and low-level security roles. A background in C and concepts like memory and call stacks is recommended before diving into assembly.

Should You Learn Assembly?

Assembly is entirely meant for very specific problems and going out of way to learn it in 2025 should only be done if you have purpose to do so and intend otget more value than the effort involved.
focus on concepts and languages that allow for more value in the same time and actually ship stuff in a timely manner.

The question “Should you learn assembly” is exactly the same as “should you learn how to drive steam locomotive”. Unless you work in museum: no.
I wrote two games in assembly as a kid, it was lot of fun, but man, that was on 8 bit computer! Over 30 years ago. There was no other way to write effective code these times in home.
Except very rare and edge cases - like low level drivers, hardware specific things which you can usually find in BIOS (or EFI nowaday), there is no need of writing direct assembly code.
Assembly code is not portable between processors and architectures - so if you write it on x86 it will not run on arm, etc. It’s clunky, it doesn’t have any data structures. If anybody need assembly then there is C. Even on arduino it’s enough.
If your code need to be written in assembly because of execution speed, then it means you are bad C programmer, or algorithm/solution is wrong, or you need to wait for faster computers :D
PS. You should know how processor work, but You don’t need to code in assembly. In this case theoretical knowledge is enough IMO.

No. Period. Tons of tech bros who don’t even speak C are printing serious money using higher level languages. Focus on creating values.

It’s already on my list after Bash scripting and CPP.

Which assembly? And, yes. You should learn one or two assembly languages, ideally for very simple CPUs.
Here’s why: You are not likely to need to write any program in assembly, which is why you don’t need to learn a specific CPU. But every developer (and system administrator) should have an idea of how the computer actually works beneath the GUIs, shells, and compilers. Learning Z80 or 6502 is enough, and both even give you a chance at writing a small program (perhaps a game) because they are simple and still alive.
Do not learn x64 or ARM64 unless you need to for some reason. But do learn 8080, Z80, 6502, ARMv1 or 8086 or 6800 or 68000 to get an idea of what’s going on.