Ramanuj kumar

Hello. Good morning. This is Ramanuj. I have, uh, 7 years around 7 years of experience into IT industry, and I have played the role of senior software engineer.

Like, uh, project management system, uh, contract management system, and, uh, and others. And I've used the language like csharp.net, vb.net, sb.net, and SQL Server, JavaScript, jQuery kind of things, dotnet core and MPC as well. Uh, if everything if we have all the documentations and everything there and if we are not able to, uh, develop it and if we are getting all the support that need to be provided, then I think we should be accountable if the project fails, uh, it is separate. Other than that, yeah, uh, I think, uh, if everything is there, documentation, uh, proper planning, proper requirement, and gathering, uh, proper setup that we need to achieve the clear goal, then I think it can be achieved.

Okay. So views are virtual tables and where the data is stored virtually, It's like data is not physically stored there. And functions functions are the routines that must return some value, one value. And stored processor are SQL saved pre compiled statement. So use b use to fetch the data from 2 or more tables and keep it for temporary. And functions, we need to write if we need to return some value, then we need to use concerns. Whereas stored processor, we use stored processor for writing the select statement, writing all those statement whether we are joining 2 or more tables. We are writing the queries. It's like sub queries, correlated queries, and and more. Alright. So, uh, it's like a function can be called, uh, inside stored processor while stored processor cannot be called inside functions. And views are it's like 2 type. 1, uh, which we can store the data physically, uh, that is materialized view and, uh, other that is virtual table, so we cannot store the data, uh, physically there. It is virtual. A stored processor is very broad, uh, in other than 2. It's like, uh, we can use, uh, uh, for security purpose also, we can use inside it the trigger and use functions, anything. And for security, we use a stored processor while we cannot use functions for security purpose as compared to a stored processor. While views can be used, uh, for security, uh, to some kind. Yeah. So we can use the deal and the email statement in the

First of all, we need to focus on the data, what we are going to, uh, validate. Right? Means what is the requirement that we need to have clear picture. Right? So and, uh, what the sources we have used to collect the data. Then after, uh, that it is the legitimate source or not. And to analyze it again, we need to confirm the sources that what we are referring. Right? So that, uh, it could lead to 100% accurate. Right? And we need to double check that data that we are going to present somewhere in meeting. So we have to speak that this is the correct or we are taking site for the data or we are presenting the data, uh, for if we are accountable for accuracy and reliability of the data. So we need to verify it from various or different different, uh, panels. Right? Different different sources. Um, I think this will help to validate, uh, the accuracy and reliability of the data, and we need to analyze it, uh, thoroughly.

Yes. Yes. We have used the I have worked with PVPI and used the razor templates. So it's like if we are writing the razor, then we are writing the CSAP and the HTML code, move the code parallelly. And to present our UI or yeah, to present our UI, we can write the result templates. And actually what happens that bvpis got created to return the data while MBC is used to return the views. Alright. So to show the views, what the data we have collected on present years earlier, we can use the result template. Yes. Uh, we have used, uh, in, uh, frequently we use the razor templates to present our, uh, UI or to showcase our data, uh, UI and building web pages.

Uh, the best practices that we, uh, need to follow or we have followed is like, uh, design pattern various design patterns, uh, right, uh, we need to follow. It's like, uh, repository design pattern, singleton design pattern, and, uh, mediator design pattern. And we also need to follow the principles, solid principles. Like, uh, right it's like, uh, SRP, uh, single responsibility principle. O for open close principle, uh, write, uh, l for Liskov Liskov C, substitution principle, I for inversion, interface regression principle and d 4 dependency inversion principle. Now it's like, we need to understand the scenario that on which scenario what we need to apply so that our project, uh, when it grows bigger, then we do not need we do not get any hurdles or on scalability side or the performance side. Right? And we we can scale it better way. So one example that we have written the code. So next thing, km1, more functionality. And we need to we need to add it. So let's see that if we are adding it and it breaks some code. Alright? Or it is just having the the previous port that we have written, uh, to implement the new features, then it is very dangerous because we would not be able to maintain those applications. Right? That's why we use solid, and it has a lot of things that we cannot complete in 2, 3 minutes. It's like a lot of things are there in solver principle. And, uh, we can also use, uh, very, uh, various, uh, guidelines, like, for naming the, uh, variables, classes, and other things. Right? Means we need to follow all those guidelines what could be in the kernel case and what would be, uh, in

Yeah. Uh, so, uh, it's like, uh, we were working in the team, and the team members asked me for some code and some help. So he was not in my team, but yes, he was sitting with me. So he asked me to solve their, uh, solve their, uh, to write code for him. And I had the time, so I have, uh, written for him. And it was, uh, it was, uh, it worked. So he told me, thank you. Right? So, uh, these are the things we, uh, if we are not, uh, responsible to write the code, even then the juniors if the juniors ask, then we need to, uh, help them because, uh, we are living in the we are working in team, so somebody is helping us. So we need to help other if we have the time. And and, uh, guide we need to provide the suggestion and guideline advice, uh, to team members and other person also if they ask me. Uh, for same, uh, because we are the social human being. So it's like and it worked fantastic. Uh, many times, it happens, uh, alright, that some juniors is asking for some advice or some code. Be right for them. It happens.

Uh, to choose abstract class or abstract functionality, we need to see that, uh, what, uh, what is our requirement. Alright. So it's like abstraction can be achieved by abstract class encapsulation also, and, uh, interface also. So let's understand that if we have some common common thing, right, so we need to put it on base class so that the derived class can access it. All the common things, we put it in the abstract class, and, uh, later we can inherit it into the, uh, derived class. And, uh, also we cannot make object of the object class sorry, abstract class. So we need to inherit it. And after that, we can use the functionality of the abstract class. So, yeah, can you explain the approach to this ID? Yeah. There is something. It's like let's one example that they are there is one company. In one company, there are multiple, uh, employee. Some employee are on the contract basis and some employer on the permanent basis. Right? So let's say every employee has some common property. Right? Uh, it's like name name, um, uh, designations, and age. Right? But, uh, the salary or the type of, uh, time that he works can be different. So we can manage that. Understand uh, please, uh, take it that, uh, example that all the common things that I have spoken could be the common that we can put it into the abstract class and the rest like permanent employees getting permanent salary. So it's like on the monthly basis and on the other hand, the contact basis, person get the employee on the hourly basis. So it's like the function would be different for, uh, both the both type of employee. Right? So, uh, all the common thing

Can you explain the delegates and events? Um, so and how do you use them? Was it in what situation? Yeah. It's like, uh, delegates are function pointer. Right? It's it can, uh, point to different different function. Right? Let's say we have created 1 delegates. Right? So we can point multiple, uh, methods, uh, and, uh, yeah, and we can take work of it. Right? Events. Events are it's like action. We create 1 events. We, uh, they click on button, and we want to get the data submitted or anything could be, uh, depending on the situation, whatever requirement is. So, uh, action happens, the event is less in system. Right? So it can be, uh, ph load or post web or anything. It would be right how you used in the main project. And definitely the event we are using event we are using for it's like submitting the data or or click and edit. Uh, click. Abstract class, uh, that we already talked about that, it is like we put all the, uh, common part. But abstract class, what happens is that we have 1, uh, incomplete, uh, abstract method and one one abstract method is, uh, must be there while one complete method could be there. Right? So, um, it's like that. And interface is like a contract. Right? There, we do not, uh, we only declare the methods and, uh, properties, but we cannot define it there. Means we are not writing all those, uh, defining all those code there. To define it, we need to inherit, implement it into the class, and we need to write all those code. So interface gives more flexibility and more security.