Nitin Jadhav

Hello. My name is, uh, and I have completed BSC IT, that is bachelor of science for in information technology from Satya College. And after that, I have worked with different companies like, uh, Virtusa, Airesource Infotech, uh, KGL, then Clover Infotech, and, uh, Debs Healthcare Solutions. And these companies have different domains. And, uh, I have total 4.9 years of experience on dot net platform. While working with these companies, uh, I have worked on different, uh, technologies like, uh, ASP dot NET Core, uh, ASP dot NET MVC. And, uh, I can do both front end and back end designing back end. So for front end, I use HTML5, uh, for the structure of the web page because that's what brow browser understands. And for styling, I use CSS 3 styling sheets. So, uh, we can separately, uh, have your own style sheet and then, uh, have your markup language and do all the that kind of things. And I have also used, uh, c sharp, uh, JavaScript lang scripting language to perform different operations on client side to handle some logic into it as well, uh, using different JavaScript concepts and, uh, functionalities. And I have also used jQuery and jQuery UI to, you know, uh, create some robust and, uh, some very good looking and, uh, very responsive websites, uh, web applications. And, uh, after that, my plan is to learn React because that is the latest React library. And it's, uh, latest JavaScript library, and it is very popular as well. I am also familiar with some concepts of it as well. And, uh, on the back end, uh, I have used dotnetcsharplanguage. I also know web APIs, different authentication and authorization techniques with identity servers. And I also know different, uh, you know, uh, I also know solid principles and architectures that we use to the to develop the application. And, uh, on back end for the database, I have used SQL. And, uh, I have created databases using store I have also used the stored procedures, transactions. And, uh, for reporting purpose, I have created different stored procedure, different set of tables. I have also even created a data warehouse system for transactional data bill, uh, for for the the for reports so that transactional level of data can be then put into the actual data warehouse because the transactional level is really granular, and we need something different, you know, like, uh, different metrics to get the get get insights into it. So for that, I use where you I have created this data warehouse. And, uh, apart from that, uh, I know little bit basics of link queue as well. And because we can use that into, uh, entity framework core, that which is I'm learning right now. I just know a little bit of it. And, uh, we can use that, uh, instead of ada.net to directly connect directly get access to the database and perform some operations through the application layer that we have.

For best practices, we use solid principles, uh, because, uh, our we we have different layers in our, uh, in our, uh, software. Right? So for designing, we we have different layer UI layer for, uh, back end, uh, getting the data from the database. We have data access layer. And, uh, then we have we have to write some business logic, which needs to be decoupled from, uh, your all of these layers that are involved into it. So for that, we need to use solid principles. And, uh, I have used those solid solid principles and to decoupled my logic from the, uh, different different layers. And, uh, and for that, uh, I have used vast use of interfaces and abstractions different abstractions because I don't want to rely on rely on concrete objects for that. And, uh, in order for a web application or something that you put on the Internet, so we also need to provide some security for that. I have used authentication and authorization techniques as well. And so, uh, so so to just support ourselves because in application people can also inject different kind of script. So in order to, uh, in order for us to be able to get, uh, uh, to cope up with those scripts, uh, we can provide some, uh, some mechanism to get to to cope up with those scripts so that we can get rid of SQL injection attacks or JavaScript attacks. We can use different kind of techniques like SQL, uh, stored procedures for that. And in order for us to make this, uh, web application a little bit faster, so for that, we can use, uh, link queue queries. When when we get the data from the database, we need to perform all sort of operations right by ourselves in it and, uh, just put that data into the different fields so that we can represent in it. So those are the practices that I have used, uh, to develop my dot net applications.

For that, uh, suppose, uh, in order for for me to file validate it, I generally go through the, uh, client go to the ticket that we I got assigned to it, uh, because, uh, there is this criteria, uh, that is mentioned that what is required in it. So according to that, uh, if my output is not competent with it or my output is not actual matched with the acceptance criteria, it means there is something wrong with it. So on the basis of that, uh, on the basis of that, uh, I can I can tell that, uh, there is something wrong in it? So I need to make some certain changes as well. And, uh, in, uh, suppose if it is a web application and, uh, uh, I need to analyze the data. So for that, uh, I I use, uh, diff I use different techniques like, uh, you know, selecting, uh, queries selecting queries and

I have worked with web API a lot. And, uh, for that, uh, I have you suppose there is this database and there is this client application, and client application, it needs data from the database. So for that, we use web API. Alright? So in order for there are different HTTP verbs for web API. For example, uh, get, put, post, delete. Those are the most useful verbs, uh, HTTP verbs. So for that, we create different controllers, and there is model binding concept. Uh, so we can pass our, uh, object to to that, uh, controllers so that we can perform different actions. Suppose we want to get the data from the the, uh, suppose that we want to get the data from the web API, we can use, uh, get west to d p verb. And for updating the data into the database, we can use post. And to, uh, delete the data from the database, we can use delete. And for, uh, and to,

Supports, uh, worst. Views. Uh, so for views, uh, we have uh, views are something, uh, that are stored into into the data database, uh, as a database object. We but do not, uh, you know, perform any DML operations in it. We just use use it to uh, get a select just, uh, in a bunch of select statements with the joints in it so so that we can use use it to join it with, uh, another tables to get the different view of the columns view of the columns and the roads. But with stored procedures, we can perform different sort of actions like, uh, you know, updating the data tables, uh, deleting the data from the tables, or, uh, you know, inserting data into the tables. And, uh, even for, uh, you know, for, uh, we can use exception handling in it. We can use transactions in it. We can use temporary tables in it. Uh, so procedures, uh, has a different a different meaning, the whole different meaning different meaning in it. Uh, so, uh, if you want to pro if you want to just take a look at the, uh, different columns and different rows, you know, then you can have a view. But with stored procedures, we want to perform different operations. And we cannot use stored procedure to join with another tables and get some different, uh, view of that, uh, rows and columns. So but with, uh, we cannot do that with stored procedure. But with, uh, but with, uh, stored procedure, we can do all sort of things. Right? And uh, we cannot pass parameters to the view on the basis of parameters. We cannot have different views. But with stored procedure, we can get different parameter. We can pass different parameters. We can have default parameters. So we can you create different, uh, different output from it. But with views, whatever we have in it, we will always get whatever there in it. We cannot change it. So that's the different, uh, that that is the difference between views and stored procedure, uh, altogether. And, uh, with stored procedure, we use create create, uh, stored procedure statement. And with views, we'll create view statement then bunch of select statements in it. So that's it.

Suppose as a developer, I am creating, uh, I am creating a, uh, city class. And in that city class, I want to get the cities. Okay. So for for I am I am I am the one who is responsible for creating that controller. Uh, so, uh, so for that, um, I'm going to create another class to get the cities from us. I can create another class. Let's say I have one class as a model where where I have city ID and name in it, and I have another class as a layer to get the cities from the database. Okay? And from that data in that class, I have a method called get cities. Now, uh, suppose there are 2 different developers who who are working on the same who are working on the same, uh, part. So, uh, if so what what what I can do is, uh, instead of just, uh, I can in my controller in in controller in my controller, in cons in that constructor, I can create object of the city class and get that the data from that, uh, method. But if I just rely on the object, then that method needs to be concrete. That class needs to be present. I know I should know the parameters to be passed it. Okay. So that needs to be done first. So until I have to wait for that. So instead of that, what I would do, I would create interface. And, uh, in that interface, I will have that method get cities. I can, uh, inherit from that, uh, in interface and, uh, use that abstract ups you know, you use that method method in my controller. I can, uh, inject that method in into my controller. Uh, just, uh, I can have a private variable of that interface reference variable. And in that, uh, I can assign that reference variable to that, uh, you know, the injected object into it. And other developer can also go ahead and get that, uh, use that interface and then provide the definition for for that, uh, get method. And he doesn't have to care about how this, uh, interface is, uh, how this method is going to be used, in which controller it it will use. He doesn't really have to care about that. Right? So in that way, I can use abstractions. So in that way, I can use our abstractions. Right? And, uh, if I want to change anything in it, uh, like, any logic in it, I don't have to care about that. That will be the part of the, uh, other developer. Uh, so we can both work independently. So this is how we can use reasonable you know, depend on the abstraction and reuse it.

So okay. Uh, so There was this scenario, uh, in, uh, in our application where, uh, uh, actually, uh, other I need to think of it. Yeah. I remember. Uh, I was working with Delta on a Delta project, uh, with Eresource, uh, Infotech, and, uh, my, uh, my manager was absent at that point of time. So it was, uh, and, uh, she needs we needed to do the deployment on the server. So, uh, instead of, uh, instead of that was her responsibility. You know? She want she was responsible for deployment. It wasn't my part. And nobody really assigned me to it, but client emailed us. So they want a new new feature in it. So I just set up meeting with the client, and, uh, uh, you know, I took I took the initiative, you know, to to do the deployment because I know how to deploy. It is just that it wasn't my part. So I just set up meeting with the client. I communicated, and I got the downtime with the client. And on the right time, uh, uh, on the decided time, I just came up, and then I did the deployment. But I I before doing that, I just, uh, you know, email other email my, uh, other upper management just to let them know that this is something that I've been doing, uh, and they they just provide they they just give me yes to do that, you know, the positive instructions. So I just did it all by myself. So that wasn't my part, and I did it. And the result was good. Everybody appreciated me. And, uh, so that's it.

Okay. Delegates are types of function pointers. So, basically, it means you can write any function which match matches with the, uh, you know, uh, the signature of the delegate. And we can we can use that, uh, function to, uh, uh, you can use a delegate to PowerPoint to that function, and it we can then invoke that function. The flexibility that it provides is that, uh, in my project, uh, I I had created this user control. And in that user control, uh, I wanted to I have add this selected change event to perform. So I I had used event, you know, event handler and just, uh, use plus equal to. Okay? Uh, selected in this, uh, let's say, selected drop down list 1 dot, uh, selected change event plus equal to new p click, uh, new event handler. So to to attach that event to that particular thing, I have used, uh, delegate, uh, event, uh, events through delegate because they work together. And uh, and, uh, I was using a I was, uh, I was having this class where where I wanted to make that class reusable. Uh, so I did not hard code the logic of a of a condition in it. Uh, there was this if condition. I do not hard hard coded the logic of that if condition, uh, because it returns blue, uh, I mean, bull, true or false, Boolean, true or false. So I just, uh, left that, uh, up to the, uh, whoever uses reuses my that class, uh, so he can, uh, use that, uh, particular class and provide his own method method to it. So in that, uh, so in about that, if condition, there was this huge, uh, method. So in that method parameter, I have I have passed a delegated reference variable so that people can, uh, you know, create their, uh, create their, uh, their own method and use that delegate. And by calling that method, they can pass their delegate to it. And they can create, uh, they can create their own method logic in it so that can be done. So if their if if their logic is bay based on that data is true, then definitely, uh, they can approve that, uh, answer in it. And in with interfaces, uh, if I want to provide some functionality of that, uh, particular thing that I can use

There wasn't any such situation for, you know, like, a failure of a project, but there were some, uh, setbacks. Uh, like, uh, there was this bug, uh, into into the ERP system where, uh, we had the functionality where where, uh, we while we were returning the products to the stock, Okay. There was this stored procedure where which creates the, uh, which actually updates the different, uh, stock. You know, after using it, we can then we can then restock it into the into this, uh, into the warehouse and stuff. So there was this functionality. So, uh, and, uh, we deployed it, and there was this bug. And, uh, so and, uh, I even after testing it, it was looking good. So there was no test test problems in it. But once we when we deployed it on the server, uh, at that point of time, uh, there was this bug. You know? So when you return the, uh, item from the from that particular for from that particular function for from that particular, I can say, job card that we have. So that that wasn't actually reflecting in it. So I was responsible for it. That wasn't a project failure. Okay? But then I acknowledge it, and after that, I solved it. And then I redeployed. Even I didn't even have to redeploy it because, uh, there was the stored procedure problem. So I just fixed it, uh, on the, uh, production server itself, And did did some testing on it, and it was solved. So there wasn't said setback, but that was okay.