Of course if your day to day job actually allows you to fully avoid bash, then by all means ignore it!
The command line is just a UI like any other - GUIs included. The way modern computers work is via API/ABI calls; via kernel syscalls and drivers separating out the responsibility of peripherals. Your command line is just an interface for managing applications that are compiled against libraries that interface with those syscalls - so in that regard using the CLI isn't any different to launching an application via a graphical icon running on a typical WIMP interface. In either case you're not making those API calls from the CLI, you're not manually managing your memory nor any of the important things that an OS does under the hood. All you're doing is using a text interface to fork() a process rather than using a mouse click to fork() a process. The difference being many CLI tools require their config supplied as command line arguments while many GUI tools don't. But even there, there are as many exceptions to that rule as there are examples of it.
I said no such thing. My point was that, if one wants to program computers, I would think one would want to be good at their job and delve deep into how their code makes computers do what they do. Showing no interest in learning the command line or the shell makes me question their interest and desire.
Saying "it's an unfortunate fact of life that programming is tied to computers" is as weird as saying "it's unfortunate that being a car mechanic is tied to cars". The job exists because of computers and cars - not in spite of it.
If you wanted a problem solving or engineering job that wasn't tied to computers then there are other options, like a mechanic, electrical engineer, mathmatition or working in any of the numerous fields of science. But a the end of the day, you're still going to need to understand the core principles of that field if you want to be effective in it.
Too often, the solution of some is only to throw more hardware at the problem.