Brijrajsinh chudasama

Yeah. Uh, Hi. Myself, uh, Richard. Uh, like, I'm having total, uh, 9 plus years of expense, basically, uh, like, particularly in c sharp, uh, background. And, uh, I'm having, uh, experience in, uh, microservices, uh, having knowledge in real Angular.

Yeah. So, uh, like, the the difference between a view, uh, function and so, which is, like, view is basically used when, like, uh, when you, like, uh, you want to store, uh, like, any particular like, basically, for select, uh, queries. So if you normally execute the same kind of query, uh, like, uh, same kind of complex query to get the result, then you can store it as a view and, like, uh, it will be precompiled, and you can use it to, uh, drive the result. And function is basically used to, like, uh, take the input and based on that, uh, execute, uh, some of the, uh, functionality. Uh, so in the view, you cannot, uh, like, take the input parameter and based on that, execute the body. But, like, in the function, you can take the input. And based on that, you can uh, based on that, you can execute the functionality. And, like, it will, uh, it will return only one result while the store procedure can accept uh, multiple input parameters as well as, like, it can return, uh, multiple result as well as it can return multiple output parameter as well. So yeah. And store procedure is also, like, uh, pre compiled. Store process can be used to do multiple group operate operations. So that's the main difference. And in the function, you can do, like, uh, multiple operation kind of thing instead of, uh, group operations. Like, uh, for example, in the function, you can do some calculation, like, number of days remaining or something like that. So that kind of, uh, functionality, uh, you can implement in the function, and, uh, we can reuse it, uh, at multiple places. While the store procedure is basically to do insert update, uh, that kind of, uh, operation with the complex logic, like, for loop and all those things, and table and all those things. That's the main difference.

Yeah. I've, uh, worked with the web API, but not, uh, like, I less experience with the razor templates. But razor templates have similar kind of, uh, similar kind of, uh, syntax like, uh, Angular and all that. So, basically, you can, uh, implement the c subside, uh, few of the c subside logic and, uh, with the HTML. Like, in the HTML, with the razors syntax, you can do you can execute for each loop for loop, and, uh, you can implement some g sharp side condition and all that thing, uh, between the razor template. Yeah. And, uh, for the web API, I have a very good experience. I also experience in micro microservices as well. So Yeah. And, uh, like, a web API, I'll use the, uh, like, a yes. I have used those, uh, web APIs to build the web page application with, like, a specifically with single page application like Angular and React, uh, as well as, uh, the web API, uh, can be used at mobile application development like that can be, uh, utilized in that.

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

Yeah. So, like, I I follow some of the best, uh, standard practices, uh, in, uh, while developing a patent application, like, uh, uh, following the, uh, coding standards and, like, uh, like, using, uh, instead of using the hard coded values, go with the constant. Whenever there is a, like, uh, when there there are, uh, there is a for loop or something like that, uh, wherever I can put the main parallel for, uh, for loop or, uh, like, uh, use multi threading, basically. So, uh, try to implement that as well as, like, uh, I get my code. Uh, like, once, uh, everything is done, I, uh, like, used to review my code with my senior or a peer person. So, uh, in case I if I missed something or, like, I'm not implement correctly, then I can, uh, improve that as well as, like, uh, normally, with all the development, I used to create test cases uh, and, uh, used to do load testing and benchmarking for that, uh, benchmarking for the course. So, uh, like, uh, the code, uh, performs well in the, uh, the load load environment. Uh, like, it gives best performance. And, uh, as well as, like, uh, and, yeah, I used to follow standard, uh, coding, uh, coding practices as well as, like, whenever there is a complex, you can use to add a minimum line of comment to explain what the the code does and, uh, following the best standard packages for routing and URL. Uh, Yeah. That's, uh, that's it, uh, for, uh, time for the web application development, like, uh, used to, uh, follow standard HTML practices. And, uh, like, currently, I am, like, uh, for the web application side and working with React and Google Earth. So, uh, like, a, uh, Angular is a full fledged framework, so following the standard practices for that. Yeah. And, also, like, implement, uh, global level and, uh, whenever required, uh, caching function or, like, a try case to handle the exception handling. So user not aware about the actual error as well as, like, a lot of the errors in the, like, database or, uh, some other places. So to, uh, to get the error logs to improve the

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

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

Yeah. So, like, uh, uh, when when there is a there is a functionality that is, uh, that is reusable, right, then we can declare it as a abstract for that we can call it as a abstract functionality. So for example, I will, uh, I will give you example, like, uh, we are if we are doing some area calculation or, uh, that kind of thing, then that can be reused in multiple, uh, multiple that can be reused in multiple places. Right? So that, uh, for that for example, we can, like, create a a abstract, uh, abstract functionality. Uh, so that kind of reusable thing for, uh, other things is, like, uh, if we are, like, converting, uh, some day, uh, some date time into some particular, uh, particular format throughout the application, then we can create that, uh, as a like, we can choose it as a functionality, And, uh, that can be reused. Uh, Yeah. So so that kind of thing that we can use throughout the application that we can, like, uh, declare as a, like, a a user data inside of the abstract functionality.

Yeah. So, like, in many places, like, when when, uh, when we are, uh, like, when we are doing the, like, uh, we are solving the some kind of bug or, uh, like, when we are implementing some, uh, kind of new functionality, and then we are going through, like, uh, some some, uh, some other other code that is developed by someone else then and, like, we go through the code again when we are debugging and, like, found out, like, this is not implemented properly, and this need to be corrected, uh, like, somewhere someone used hard coded values or, like, uh, something something, uh, somewhere. Uh, h case scenario is not covered in that, uh, that particular, like, code area. Then I I'm taking initiative and, like, uh, and solve the problem that wasn't even, like, a part of my job or, like, a part of my task. Right? But still, like, uh, we used to like, even even in, uh, like, when we are integrating with some other component, then we find out that this particular, uh, already developed component is giving for common issue or, uh, not covering some edge case scenario or, like, that then, uh, also, I'm taking responsibility and, like, uh, taking ownership and solving it. Yeah. Also, like, when when we are testing our our our new implementation or or something, then we need, like, a in the UI part or somewhere, we make, like, a something like a some some device, it is not working. That kind of thing as well if we find out during our testing, then, uh, we can take the ownership and solve it.