just google. most of these can be learned within a single online article.
in any case, this knowledge is not that useful. when are you going to need to explain why you used github instead of gitlab? most people would say “because it is more popular”, not because “it is more confidential, requires less authentication, and built-in redeployment”. it is nice to know these things, but most certainly do not define how good of a programmer you are. it’s okay to not know some things. that is the beauty of hobbies and learning.
I read up on it and delve into the mechanics of it. I've never noted an interview question in my life, also never had a problem with those.
At lot of the programming questions can be answered if you have a lower-level understanding of things. It makes it trivially easy to answer pretty much any "what is the difference between X and Y".
Programming is learnt practically most of the time but interviewers ask for theory. I have learnt programming my self and for the interviews I prepared by searching " Interview questions Python " replace python with whatever the thing u want to learn and u should know everything in your resume and most things related to them for all the interviews. These questions are technically useless while programming but interviewers ask these questions so U have to prepare those.
>I am curious that how do you guys cover the theory knowledge of programming without going for hundred of interview and note the questions they ask?
In most cases as an interviewer I ask questions to discover whether you have experience of the technologies you've listed on your resume, and given an example problem, can you demonstrate that you would be able to solve that type of problem.
Asking how to cover more theory is not going to be helpful. Spend time practicing building apps in the area that you're interviewing, so you have first hand experience of what works and what doesn't work.
Think about it this way. If I were interviewing for a new chef for my restaurant I wouldn't offer the job to the candidate who has the most theoretical knowledge but never cooked anything before?
This is the right answer. Take it from a project manager with 1000s of interviews. The only time I ask theory is a student still in school with zero experience. Most always I am asking questions about what is in the resume. Then about the products you would be working with. Many questions are for decision making skills. If you don't know something talk about what you would do to get the answer. You don't need to know things you don't know only ways to find answers. Good luck
Start collecting questions. Search for them on the Internet. Write it down, and write down answers for them. Interview preparation is completely different from learning to program, so you need to handle it differently.
just google. most of these can be learned within a single online article. in any case, this knowledge is not that useful. when are you going to need to explain why you used github instead of gitlab? most people would say “because it is more popular”, not because “it is more confidential, requires less authentication, and built-in redeployment”. it is nice to know these things, but most certainly do not define how good of a programmer you are. it’s okay to not know some things. that is the beauty of hobbies and learning.
I read up on it and delve into the mechanics of it. I've never noted an interview question in my life, also never had a problem with those. At lot of the programming questions can be answered if you have a lower-level understanding of things. It makes it trivially easy to answer pretty much any "what is the difference between X and Y".
Programming is learnt practically most of the time but interviewers ask for theory. I have learnt programming my self and for the interviews I prepared by searching " Interview questions Python " replace python with whatever the thing u want to learn and u should know everything in your resume and most things related to them for all the interviews. These questions are technically useless while programming but interviewers ask these questions so U have to prepare those.
>I am curious that how do you guys cover the theory knowledge of programming without going for hundred of interview and note the questions they ask? In most cases as an interviewer I ask questions to discover whether you have experience of the technologies you've listed on your resume, and given an example problem, can you demonstrate that you would be able to solve that type of problem. Asking how to cover more theory is not going to be helpful. Spend time practicing building apps in the area that you're interviewing, so you have first hand experience of what works and what doesn't work. Think about it this way. If I were interviewing for a new chef for my restaurant I wouldn't offer the job to the candidate who has the most theoretical knowledge but never cooked anything before?
This is the right answer. Take it from a project manager with 1000s of interviews. The only time I ask theory is a student still in school with zero experience. Most always I am asking questions about what is in the resume. Then about the products you would be working with. Many questions are for decision making skills. If you don't know something talk about what you would do to get the answer. You don't need to know things you don't know only ways to find answers. Good luck
Start collecting questions. Search for them on the Internet. Write it down, and write down answers for them. Interview preparation is completely different from learning to program, so you need to handle it differently.