Nitin Jadhav

Hello. My name is, and I have completed a BSC in Information Technology from Satya College. And after that, I have worked with different companies such as Virtusa, Airesource Infotech, KGL, Clover Infotech, and Debs Healthcare Solutions. And these companies have different domains. And I have total 4.9 years of experience on the dot net platform. While working with these companies, I have worked on different technologies like ASP dot NET Core, ASP dot NET MVC. And I can do both front end and back end designing. So for front end, I use HTML5 for the structure of the web page because that's what a browser understands. And for styling, I use CSS 3 styling sheets. So, we can separately have our own style sheet and then have our markup language and do all that kind of things. And I have also used C sharp, JavaScript, and scripting languages to perform different operations on the client side to handle some logic into it as well, using different JavaScript concepts and functionalities. And I have also used jQuery and jQuery UI to create some robust and very good looking and very responsive websites, web applications. And after that, my plan is to learn React because it is the latest React library. And it's the latest JavaScript library, and it is very popular as well. I am also familiar with some concepts of it as well. And on the back end, I have used the dot net c sharp language. I also know web APIs, different authentication and authorization techniques with identity servers. And I also know solid principles and architectures that we use to develop the application. And on the back end for the database, I have used SQL. And I have created databases using SQL Server. I have also used stored procedures and transactions. And for reporting purposes, I have created different stored procedures and different sets of tables. I have also even created a data warehouse system for transactional data and bills, 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, like different metrics to get insights into it. So for that, I created this data warehouse. And apart from that, I know a little bit about linked lists as well. And because we can use that into entity framework core, which is what I'm learning right now. I just know a little bit of it. And we can use that instead of ADO.NET to directly connect and get access to the database and perform some operations through the application layer that we have.

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

For that, suppose, in order for me to file validate it, I generally go through the client's ticket that I was assigned to, because there is this criteria that is mentioned, which outlines what is required. According to that, if my output is not competent with it or my output does not match the acceptance criteria, it means there is something wrong with it. On the basis of that, I can tell that there is something wrong in it. I need to make certain changes as well. And suppose if it is a web application and I need to analyze the data. So for that, I use different techniques like selecting queries and using diff.

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

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

I am creating a city class. In that city class, I want to get the cities. So for that, I am the one who is responsible for creating that controller. So for that, 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 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, suppose there are 2 different developers who are working on the same part. So, if so, what I can do is, instead of just creating an object of the city class in my controller, I can create an object of the city class in my controller and get that data from that 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 to it. Okay. So that needs to be done first. So until I have to wait for that. Instead of that, what I would do is create an interface. And in that interface, I will have the method get cities. I can inherit from that interface and use that method in my controller. I can inject that method into my controller. Just I can have a private variable of that interface reference variable. And in that, I can assign that reference variable to the injected object into it. And other developers can also go ahead and use that interface and then provide the definition for that get method. And they don't have to care about how this interface is used, in which controller 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 if I want to change anything in it, like any logic in it, I don't have to care about that. That will be the part of the other developer. So we can both work independently. This is how we can use reasonable dependency on the abstraction and reuse it.

So okay. There was this scenario in our application where I was working with Delta on a Delta project with Eresource, Infotech, and my manager was absent at that point of time. So it was, and she needed us to do the deployment on the server. Instead of that being her responsibility, you know? She was responsible for deployment. It wasn't my part. And nobody really assigned me to it, but the client emailed us. They wanted a new feature in it. So I set up a meeting with the client, and I took the initiative to do the deployment because I knew how to deploy. It just wasn't my part. So I set up a meeting with the client. I communicated with the client, and we agreed on a downtime. On the agreed time, I came up and did the deployment. Before doing that, I emailed other upper management to let them know what I was doing, and they gave me positive instructions. So I did it all by myself. That wasn't my part, and I did it. And the result was good. Everybody appreciated me. And so that's it.

Delegates are types of function pointers. So, basically, it means you can write any function that matches with the signature of the delegate. And we can use that function to invoke that delegate. The flexibility that it provides is that in my project, I had created this user control. And in that user control, I wanted to add this selected change event to perform. So I had used an event handler and just used the += operator. Okay? Selected in this, let's say, selected drop down list 1's selected change event += new System.Windows.Forms.MouseEventHandler(new EventHandler). So to attach that event to that particular thing, I have used a delegate because they work together. And I was using a class where I wanted to make that class reusable. So I did not hard code the logic of a condition in it. There was this if condition. I did not hard code the logic of that if condition because it returns a boolean value. So I just left that up to the whoever uses my class, so he can use that class and provide his own method to it. So in that if condition, there was this huge method. In that method parameter, I passed a delegate reference so that people can create their own method and use that delegate. And by calling that method, they can pass their delegate to it. And they can create their own method logic in it so that can be done. If their logic is based on that data is true, then definitely they can approve that answer in it. And with interfaces, if I want to provide some functionality of that particular thing I can use.

There wasn't any situation like a failure of a project, but there were some setbacks. Like, there was a bug in the ERP system where we had functionality to return products to stock. There was a stored procedure that updated the stock. After using it, we could restock it into the warehouse and so on. So, there was this functionality. We deployed it, and there was a bug. I even tested it, and it looked good, with no test problems. But once we deployed it on the server, there was a bug. When you return an item from a particular job card, it wasn't reflecting in it. I was responsible for it. That wasn't a project failure. But then I acknowledged it, and after that, I solved it. I redeployed it, and I just fixed the stored procedure problem on the production server itself. I did some testing, and it was solved. There wasn't a setback, but that was okay.