How well does a backend developer need to understand Linux?

Question

linux

I stayed on Windows, now I installed Ubuntu. I decided to improve my knowledge in this OS. What should I study to improve the quality of my work, as well as to be a plus in further employment?
At the same time, I don’t really like poking around in the system, I like to write code more.
What can I do:

• the most basic commands like ls, cat, ln, sed, dpkg, apt, nano;
  
• install and configure php, nginx, mysql. And then the level: sudo apt install php-cli, php-curl, .... Never built from source
  
• general directory structure: what is /etc, /var, /usr, ...
  

What I can't do (in general, everything else):

• if after rebooting the system does not boot, or the GUI does not boot, then I will not be able to fix it
  
• can't fix any bug without google
  
• write some complex and long commands in one line
  
• I don't know bash/sh well, I don't even know how they differ; I can't use vim
  
• compile from source
  

When I go to some ENT, it starts to seem that I am immensely stupid - there everyone will rebuild the kernel for you, and solve any problem without Google, and the code is written only in vim / emacs, and, in general, some dialogs there are not even clear: )

Answer 1

You need to compile from source in very rare cases, so rare that you don’t need to know how to do it at all. So you can safely dismiss this skill.
It is necessary:
​​To know where what logs are and be able to read them, solve errors.
All sorts of banal things, such as starting / restarting the daemon, killing the process, being able to read bash scripts and writing a little (tweak something at the level and so as not to break everything to hell)
For a backender, you need to be able to install and configure the software with which you work : nginx, apache, mysql, postgres, redis, mongodb and so on.
You may not know Vim at all, in * nix there is usually a simpler editor, such as nano, joe or mcedit in general.
The most important thing is to learn how to exit vim before you mess up the file ;-)
If you work with a language that has its own package manager (npm, yarn, pip), you need to be able to install it and resolve installation errors through these package managers.
For example, python-pip requires the compiler and python header files to be installed. I mean, you need to know such subtleties.
ssh, of course, you need to be able to configure, generating keys, setting up authorization by key, copying scp files.
git set up bare repositories to upload to the server and deploy there, when working without third-party services such as github, bitbucket.

Answer 2

Must be able to set up the environment for your application.

Answer 3

Bash scripts - you don't have to be able to write, but you do need to read. It is desirable to be able to use python - it is almost always present in the system and it is more digestible than bash magic One -liners
for bash - 2-10 pieces are better to have in memory or have your own bash_aliases with such blanks. For parsing logs, bulk renaming, moving, optimizing
Compiling is not terrible if you only need ./configure && ./make. More important is your ability to read the build script and understand how to enter your settings. Building from apt-sources is even easier
Rebuilding the kernel is not often practiced and is more likely for very fine tuning or it is done from a one-liner copied from Google just for fun. Try to screw up a couple of times on a virtual machine and understand how to do it
vim - that you definitely need to know how to write, save, exit, and exit without saving. Wim is not the tool to use when stepping over yourself
In Linux, the main thing to be able to do is the ability to read logs

Answer 4

There is a special specialist for this - Devops, he should have a good start in system administration.