During the interview, the interviewer may also ask these questions. Of course, the important thing is not that you can write the code correctly, but that you have the right idea. Because there may be many different implementations of the same case, the interviewer may not be able to see whether there is any problem with the code you wrote. The key is that you can explain your ideas clearly to the interviewer.
Of course, it is also possible that the interviewer will give you a computer that is not connected to the Internet and let you program on the spot, so you still have to write more. If you have been working for several years and most of the things you do are just copy and paste, then you will probably fail in such an interview.
If you think patiently, you can still write it. It’s just that after working, I have been programming for Google. What you want is to complete the work as quickly as possible. The boss doesn’t care whether you came up with it or copied it from somewhere. Then it gets better and better. I am getting more and more impatient. For another example, I bought a bunch of books and got distracted after reading a few lines. Eh...
To be honest, the code I write is becoming more and more object-oriented. Not to mention programming for Google, it is basically programming for API. No need to think about anything, just know which method does what and call it. When you want to take the time to look at the source code of these encapsulation methods, the demand comes again. Work a lot on business every day, not code. There is a saying that many people agree on: Technology is actually not a big problem, and you can solve the problem by spending some time and learning now.
Same feeling... Nowadays, I have forgotten a lot of those low-level things, and the API can be checked and used immediately. I am impatient to look at various algorithms
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
During the interview, the interviewer may also ask these questions. Of course, the important thing is not that you can write the code correctly, but that you have the right idea. Because there may be many different implementations of the same case, the interviewer may not be able to see whether there is any problem with the code you wrote. The key is that you can explain your ideas clearly to the interviewer.
Of course, it is also possible that the interviewer will give you a computer that is not connected to the Internet and let you program on the spot, so you still have to write more. If you have been working for several years and most of the things you do are just copy and paste, then you will probably fail in such an interview.
It’s so normal. Without an IDE, I might even write the wrong grammar :)
I have been working for 3 years and now I can’t even write the 9*9 multiplication table.
It’s normal. I don’t use these much in my work. I focus more on ideas!
If you think patiently, you can still write it.
It’s just that after working, I have been programming for Google.
What you want is to complete the work as quickly as possible. The boss doesn’t care whether you came up with it or copied it from somewhere.
Then it gets better and better. I am getting more and more impatient.
For another example, I bought a bunch of books and got distracted after reading a few lines. Eh...
To be honest, the code I write is becoming more and more object-oriented. Not to mention programming for Google, it is basically programming for API.
No need to think about anything, just know which method does what and call it.
When you want to take the time to look at the source code of these encapsulation methods, the demand comes again.
Work a lot on business every day, not code.
There is a saying that many people agree on: Technology is actually not a big problem, and you can solve the problem by spending some time and learning now.
Okay, that’s a lot of nonsense.
Same feeling... Nowadays, I have forgotten a lot of those low-level things, and the API can be checked and used immediately. I am impatient to look at various algorithms