[LINUX] The story of the learning method that acquired LinuC Level 1 with only ping -t


I think it's the season when new employees have finished their training and are getting used to the company. You may be in trouble, such as not knowing how to study for qualifications as told by the company. I will write the study method I did, hoping that it will be helpful when aiming to acquire qualifications such as Linux. If the difficulty level is about Linuc Level 1, I think it is possible to pass with just ping -t like I do. By the way, it's okay to buy a thick book, but I don't read much because of my annoying personality, and it's treated as something I didn't have.

table of contents

――The number of questions is small, first read and understand rather than -Look at and remember the reason for the mistake --Do not aim for perfection

I will proceed with the above three.

The number of questions is small, first read and understand rather than

After solving the specified number of questions, ping -t will display the answer results.

The problem explanation page is

Commentary: ~~~~~~~~~~~ ~~~~~~~~~~~ reference: ~~~~~~~~~~~ ~~~~~~~~~~~

It is described in the flow. In most cases, the will give you an overview of the area in question. If you don't understand the problem, you can read it in the order of to speed up the understanding. Also, even if the question was answered correctly, I tried to read it without reading it carefully.

At first, I started with 5 questions. At the beginning of learning, there are many things you don't understand. In this state, rather than solving many various problems, narrow the interval between exercises and answers as much as possible. Priority is given to fixing the contents written in to the memory.

If the percentage of correct answers increases, gradually increase the number of questions, and if you switch fields, start from 5 questions again ... Was repeated in all fields.

Learn the reason for the mistake while looking at the

Ping-t has many choice questions of about 4 to 5 questions. If you solve a problem many times, you may find the answer to the problem somehow. Depending on the problem, the also describes the reason for the mistake. Let's not let this flow.

At the same time as choosing the right answer, think about what's wrong with the other options. There are different order of specification, different command options, etc. With regard to command options, you can solve several questions with one problem by solving while thinking about "what kind of function is the option of the wrong option". Isn't it a good deal?

Don't aim for perfection

You should pass this exam if you have a correct answer rate of about 65%. So don't keep pinging for perfection. In my case, I received 101 after taking 80% of the mock exercises many times, but I felt that it took too much time. One month later, 102 took the test with the feeling that "it would be enough" when he took more than 70% of the mock exercises about 6 or 7 times. Both passed with sufficient scores, and there was not much difference in the percentage of correct answers. Whether you pass with a 100% correct answer rate or a 70% correct answer rate, there is no difference in the results of passing. But time is finite. The time you spend doing what you like is also important to avoid stress.

・ What percentage should I pass? ・ How many questions can I make a mistake?

Let's schedule the exam after considering.

Recommended Posts

The story of the learning method that acquired LinuC Level 1 with only ping -t
The story of doing deep learning with TPU
The story of displaying images with OpenCV or PIL (only)
A story stuck with the installation of the machine learning library JAX
The story of making a module that skips mail with python
A story that visualizes the present of Qiita with Qiita API + Elasticsearch + Kibana
The story of making a web application that records extensive reading with Django
The story of low learning costs for Python
See the behavior of drunkenness with reinforcement learning
The story that fits in with pip installation
A story that reduces the effort of operation / maintenance
The story of stopping the production service with the hostname command
A story that struggled with the common set HTTP_PROXY = ~
Predict the gender of Twitter users with machine learning
Summary of the basic flow of machine learning with Python
Record of the first machine learning challenge with Keras
The story that the return value of tape.gradient () was None
The story that Japanese output was confused with Django
A story that analyzed the delivery of Nico Nama.
Script that changes the length of the sound with REAPER
Create a bot that only returns the result of morphological analysis with MeCab on Discord
I made an API with Docker that returns the predicted value of the machine learning model
The story of sys.path.append ()
The story of implementing the popular Facebook Messenger Bot with python
Decorator that displays "FIN method name" at the end of the method
The story of rubyist struggling with python :: Dict data with pycall
The story that Python stopped working with VS Code (Windows 10)
The story that the private key is set to 600 with chmod
The story of making a question box bot with discord.py
The story of creating a bot that displays active members in a specific channel of slack with python