You don't even know what kind of architecture your code is going to work on. It might be a one-core single-threaded legacy machine, it might be a virtual machine, it might be a bytecode-executing runtime thing, like Graal VM. Knowing architecture might make you a better embedded or real time software engineer, or even a mixed software-hardware architecture designer. If you are creating any kind of software nowadays, what you write is so far away from the actual architecture that you might as well guess it's running on a Turing-complete cellular automata. You don't care.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You don't even know what kind of architecture your code is going to work on. It might be a one-core single-threaded legacy machine, it might be a virtual machine, it might be a bytecode-executing runtime thing, like Graal VM. Knowing architecture might make you a better embedded or real time software engineer, or even a mixed software-hardware architecture designer. If you are creating any kind of software nowadays, what you write is so far away from the actual architecture that you might as well guess it's running on a Turing-complete cellular automata. You don't care.