Brijrajsinh chudasama

Yeah. Hi, I'm Richard. I'm having nine plus years of experience, basically, particularly in C#. And I'm having experience in microservices, having knowledge in real Angular.

Yeah. So, the difference between a view and a function is that view is basically used when you want to store any particular result for select queries. So if you normally execute the same kind of query to get the result, then you can store it as a view and it will be precompiled, and you can use it to drive the result. A function is basically used to take the input and execute some functionality based on that. But in a function, you can take the input and based on that, execute the body. In a view, you cannot take the input parameter and execute the body. In a function, you can execute multiple operations, such as calculations, like the number of days remaining. That kind of functionality you can implement in a function and we can reuse it at multiple places. While a stored procedure is basically used to do insert, update, and other operations with complex logic, like for loops and all those things, and tables. That's the main difference.

I've worked with the web API, but I have less experience with the Razor templates. However, Razor templates have similar syntax to Angular and all that. So, basically, you can implement C# logic and with the HTML. In the HTML, with Razor's syntax, you can execute a for loop, and you can implement some conditional statements between the Razor template. Yeah. And, for the web API, I have very good experience. I also have experience in microservices as well. So, yeah. And, like, a web API, I'll use, like, yes. I have used those web APIs to build web page applications, specifically with single-page applications like Angular and React, as well as, the web API can be used in mobile application development, which can be utilized in that.

Yeah, so not as a project failure, but as a one component failure, I had experience in one component where we had misunderstood, I misunderstood business logic, actually. So because of the business logic running differently, we implemented it in a different way. And that was even working fine, but it created a performance issue after some time, because I didn't understand, I just assumed a number of maximum requests or maximum customers at a time, but in the actual environment, it was more users and more simultaneous requests at a time. So at that time, it was a kind of setback, not a failure, but I had to spend some time to update and boost the performance of that particular component and then it worked fine. That's one kind of recent example with me.

Yeah, so I follow some of the best standard practices while developing a patent application, like following the coding standards and using constants instead of hard-coded values. Whenever there's a for loop or something similar, I try to implement a main parallel for loop or use multi-threading. So, I try to implement that as well as I get my code. Once everything is done, I review my code with my senior or a peer person. In case I missed something or I'm not implementing correctly, then I can improve that. Normally, with all the development, I create test cases and do load testing and benchmarking. So, the code performs well in the load environment, it gives the best performance. And, as well as, I follow standard coding practices. Whenever there's a complex part, I use a minimum line of comment to explain what the code does and follow the best standard packages for routing and URL. That's it for the web application development, I follow standard HTML practices. Currently, I'm working on the web application side with React and Google Earth. So, Angular is a full-fledged framework, so I follow the standard practices for that. And, I also implement global-level caching functions or try-catch blocks to handle exception handling. So, users are not aware of the actual error, as well as, a lot of errors in the database or other places. To get the error logs to improve the code, I do that.

Yeah. So, basically, to validate the accuracy and reliability of the data, we have certain parameters, for example, there is a URL number or some kind of a number, then first of all, doing validation, the data or data type should be matching, if there is a particular length or some kind of fixed length, then we have to validate the length parameter as well as the data type parameter and it should be placed. And that kind of validation will help. We can also validate the data with the sample example of the valid data, then we can based on that do certain validation, for example, some GUI ID or some of that kind of thing. So we can validate. So that way, we are checking for example, if some data, like country data or city data, that kind of thing is coming, then we can check for the accuracy in existing tables to map them and whether they are correct or not. And for reliability and analysis before presenting the data, basically, I used to go through this, so we can manually validate as well as we can have a set bunch of data. So with that, we can validate our data before analysis to confirm if it is reliable data or correct.

Yeah, so delegates are basically kind of pointed to a function. Delegates are like a reference, they define with the delegate keyword and in that, we have to define which function it will be pointing to. So basically, delegates, I've used it. I'm not able to actually remember, but I used delegates in many places. Yeah. Events, I'm not able to recall right now where I use the events. Yeah. And in what kind of scenario I'll go with the interface, type of extra class. So basically, the extra class, I'll use wherever, like, for some of the methods, we needed to define some of the functionality like we want to define some, we want to like define some of the functionality of the particular method, then I'll go with the abstract class. If we want to go with a low implementation at all, just like a blueprint, then I'll go with the interface. Interface and wherever we have to do multiple things, then basically, we have to go with the interface only. And, yeah, explaining about the collection in, like yeah. So bandwidth collection is basically done automatically by the C# to free up the memory. Like, basically, it will free up the memory. So whenever there's a generation, then it's in 1, 2, 3. So if something is out of the scope of particular coding, then and if it's like that particular thing is no longer needed, then garbage collection will automatically figure out that memory. If it's a lot passed in the 1st generation, then it will go to the 2nd generation.

So, when there is a functionality that is reusable, then we can declare it as an abstract, which we can call an abstract functionality. For example, if we are doing some area calculation or that kind of thing, then that can be reused in multiple places. Right? So, for that example, we can create an abstract functionality. That kind of reusable thing is also if we are converting some date, some date time into some particular format throughout the application, then we can create that as a functionality, and that can be reused. So, that kind of thing that we can use throughout the application, we can declare as a user data inside of the abstract functionality.

Yeah. So, in many places, when we're solving a bug or implementing new functionality, and we go through other code developed by someone else, and we're debugging and find out it's not implemented properly, and it needs to be corrected, sometimes someone used hardcoded values or something, and a certain scenario isn't covered in that code area. Then I take initiative and solve the problem that wasn't even part of my job or task. But still, when we're integrating with another component, we find out it's giving a common issue or not covering an edge case scenario, and then I take responsibility and ownership and solve it. Yeah. Also, when we're testing our new implementation, we need something in the UI part or somewhere, we make a device, and it's not working. That kind of thing as well if we find out during testing, then we can take ownership and solve it.