Answer the question
In order to leave comments, you need to log in
What does "knowledge of linux" mean in vacancies for a web developer position?
Where is this line beyond which you can say that I know linux? Suppose such a requirement for the position of a C / C ++ developer raises no questions, but when I see this requirement (and in a specific formulation) in vacancies for the position of a php or python web developer , I immediately become perplexed.
Answer the question
In order to leave comments, you need to log in
IMHO, I think that this means you need to be able to raise your software / scripts on the server.
Know what ssh/ftp is and how to use it.
And of course how to do apt-get install nginx php-fpm
How to buy / bind a domain, how to set it up on the server and all that.
If the developer does not know how to do this, then the question arises how does he make websites at all?
Because I met a front-end developer who made round eyes when he was told to upload something on ftp.
And this caused confusion in me.
It seems that he does everything on the local server, but he didn’t even know how to log into the server, what he did before and how he worked without a clue.
I think knowledge of linux means basic knowledge of the user, such as:
As for package management .... I don’t know, IMHO this is not necessary. Well, if you are growing on your own, you will probably learn such things anyway, but for hiring it should not be a serious criterion - preparing a development environment is not a developer's task, but a devops or, at worst, a team leader.
Simple questions.
How to create and edit a text file directly on Linux.
How to log into Linux remotely.
How can I go to Linux and run a php file there for execution?
How to see logs?
It is perfectly normal if you are an advanced user on Linux - you can install a program on Windows, stop / start a service, copy a file from one Windows to another remotely?
That's all the same, repeat on Linux and consider that you have a basic minimum.
In principle, knowing the environment in which the backend works is always beneficial. It's easier to explain to the admin what you need, it's easier to understand where you need to "click". Between the front and back there are still places where you can program. In addition, admins may not know the intricacies of the settings and can set the default settings. I have one application server running at work. On tomcat. We allocated 16GB of memory on the virtual machine, launched it. And he worked for more than one year before I joined the company. When I saw a config - ofigel. The memory was allocated by default. 2GB. So do not think that if something is not your responsibility, then you do not need to be able to check.
Let me give you advice - keep records of your achievements, screenshots. This approach has helped me many times. Showing once again at the interview that you can really document something and share it is definitely a plus at the interview. Maybe even a future employer will see how you dealt with a topic familiar to him - it will be easier to find a common language with him.
This is the level of a confident user - the ability to install packages from the repository, basic knowledge of the shell. If a full-stack or back-end developer - then install and configure the web server and database.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question