Відео

Yes sure. It should only be understandable

@@noorcodelogics yes

It depends upon the interviewer. It's not necessary that everyone will ask the same questions as it's not possible to cover the whole .NET in a single video. Thanks for your suggestion.

Yes sure. Please fill the form in the description

Will try to improve. Thanks for your suggestions

Sir it's paid

@@noorcodelogics ok thank you

Thanks 🙏

Yes sure. Will upload soon

Thank you so much

Yes Sure. Searching candidates who are willing. 🔎

Thanks for your appreciation. I will try to upload with more details and practical coding examples by screen sharing.

Nice to hear about this. Thanks for providing the solution about.

Thanks Sir. The whole series is coming and I will try to explain all the basics.

Yes CLR is responsible for lots of tasks.

www.linkedin.com/in/nooruddin-dotnet-dev

Thanks

Thank you for your feedback. The purpose of this video is to highlight some of the most important theory-based questions often asked during .NET interviews. While it's true that interviewers won't ask all the questions covered, knowing these can help you prepare for the theoretical aspects of interviews. Regarding your point about practical problem-solving, you're absolutely right. Interviews typically have multiple phases. In the initial phase, interviewers often focus on theoretical knowledge and general concepts. Subsequent phases usually involve practical tasks and project implementations. Finally, you may also have interviews with upper management, clients, or HR. I appreciate your suggestion, and I plan to cover more coding and practical problem-solving in future videos. This video is meant to prepare you for the theory questions that are commonly asked in the first phase of interviews to gauge your understanding of the technology.

You stuck in waterfall ERA now we are in AI ERA DUDE lets upgrade if you didn’t memorize how you write code 😮… for sure at-least you should aware of interfaces & its implementation methods

@@jackdesparrow4783 👍 Thank you for your input! It's really important to balance knowing theoretical concepts with practical problem-solving skills. Both are essential in today's tech and AI world.

@@jackdesparrow4783 I'm not sure what you're talking about, implementation of methods and interfaces has nothing to do with the era either it's the AI era or the Stone Age! Don't make up philosophy. One should know the concept and how to implement the logic not the method name itself. Either "InvokeNext" or "Invoke" names make sense as long as the developer wants to hand over the process to the next middleware. I'm just saying that asking about the method names is a waste of time because there are an enormous number of interfaces and more of their implementations. One should know how to use it or they should search for it as long as they know the action they want to take. Having them all in their mind is not even possible or useful. Free your mind and focus on the solution and logic of the flow, rather than the name of the method. Knowing that there is some method lying in a library which does that logic is enough, the rest can be done with IntelliSense or searching.

L mk iuu7d😊 Kaka

Yes sure, next time we will be sure to add coding questions and screen sharing. Thanks 🙏

Sure Mustafa Bhai. It was just a start. Will try to focus on code part in future. Finding candidates who are willing to appear 🥲

Please sir provide a detailed video it's a humble request 🙏

Hi, That's a very good question. When we start new jobs in software houses, we often have to work on existing projects or products. If the product codebase is very large, it can be challenging to understand it quickly. In well-structured and organized companies, they usually provide enough initial time, at least two weeks, to familiarize yourself with the product. During this period, you won't be given very complicated tasks. Instead, you'll be assigned simpler tasks under the supervision of a team lead. Gradually, as you complete the three-month probation period, things will become clearer. Sometimes, organizations may extend the probation period if performance is not satisfactory. In short, you'll learn step by step, and they won't overwhelm new joiners. However, in many software houses, especially startups, there may not be much time for learning, and you might be directly assigned complex tasks. In such cases, communicate well with your team lead or project manager, and ask for the necessary guidelines or understanding regarding the task.

Sure I will. Plz read the details message here in the reply.

@@noorcodelogics Ok Thank you 🙏

@@noorcodelogics Thanks 🙏

Thanks 🙏

I am really sorry for this. Actually, I did not get this when uploading the last two videos. I think the editor created the issue. I will surely check next time before uploading. Thanks for mentioning

No issues keep uploading ​@@noorcodelogics

It always helps me . Thanks 🙏

You have to debug the code for identifying issue

Thanks. Keep your learning ON 🎇

When joining a new organization as a software developer, it's normal to be unfamiliar with the existing code structure. Even experienced developers require time to understand the architecture and workflow of a new product. However, having a solid grasp of the technology stack can help you troubleshoot and identify code-related issues more quickly. Sometimes, you may find the root cause of a problem, but lack the business context to decide how to proceed with a fix. In such cases, it's essential to consult with business stakeholders to determine the appropriate course of action. Collaboration between developers and business teams is crucial for ensuring that code changes align with broader organizational goals. This approach allows you to resolve issues effectively while maintaining a clear focus on business requirements.

There is a video in the list. Plz watch

Sir I don't have the source code at the moment, unfortunately. Thanks

Thanks I didn't try it personally 😕

Sir source code is not available at the moment. I am really sorry 😞