Rahul Senapati

Uh, well, uh, thank you for allowing me, uh, for having an interview in a particular domain. Uh, for this position, I'm gladly immense to be applied for this particular position. Myself, Rahul, Shrikant, Sanapati, with having a result driven 10 year experience in dot net platform, where I have been working on several technical skill such as dotnetcore, which will which is the latest version, asp.netmvc, asp.net, all platform technology, c sharp, vb.net as a programming languages as well as a database, as well as Oracle. So, uh, in my entire journey of 10 year experience, I have a vivid domain knowledge. Now you can say that banking, finance, health care, insurance, and, plus, in my previous organization, I was working in oil and gas sector. The second most advantageous thing what I have been into that in my previous organization where I have to develop a software from a scratch. So I have to put myself into different different particular role to develop a software from scratch. It means that you have to do your analysis. You have to do a customer acquisition, discussing with the business team for the functionality, develop the documentation framework, how the approach should be in the hybrid model, do your development, do your testing, uh, do an act of a project manager while discussion purposes there with the business functionality, then deploy in the solution environment. So I've been into each and every particular role to do that particular, uh, examine. Now coming to the back, uh, in the technology that I have been working to that I have already been mentioned, I have working to software like entity framework. I have worked on DevOps for CICD pipeline in Azure as well as GitHub. I also work in particular, uh, you can say, in Azure Cloud, such as Azure function, Azure service, logic app, Azure Redis app for, uh, catching purpose for the high intense application purposes. That's all that guy and I say. Now in terms of having a domain knowledge, you can have a review of my profile so that you can get a better understanding to it. And that's all from my side today. Thank you.

What? So what are the some practice that you've been following when they're looking dot in particular So while considering this particular question, so I have to understand the particular architecture, the concern behind that particular web development, what it would be. First, we need to understand the architecture. So when we have the framework, the documentation part or any kind of change because we need to understand the architecture is even in the high intense application, even in the any fi any kind of architecture performance. Then we need to understand that we that that's what a high level, uh, design format. Then then we need to break it into a low level design format where we need to see how we can fix it or how we can draw it in terms of having into a design pattern or with the help of including a solid principal in it. So these are the particular areas that we need to withdraw upon to check if everything seems lengthy and resilience in terms of having or creating a good architecture software. If we follow this certain kind of thing, then we are good to go, and we don't have a a long back end error for a long duration if we follow this kind of strategy.

Uh, that would be a concern. Now that would be a good question to ask on this how for a project failure. That that might be a question where you have done certain thing in terms of your deployment or in terms of a certain functionality which you are not withdrawn upon or which is not up to the expectation that they have been drawn. In that, we have to know that certain, uh, recurring thing won't be happen once again once we have drawn into it or keeping in mind. And that's the thing that we need to be checked upon. So we need as for this failure account, as when you say, we need to be, uh, have a weekly or monthly review so that everything should be in line upon for the project purpose and for the tracking purposes so that, uh, majority of your project failure concern would get removed off.

So now the coming point, your question for this, the accuracy and reliability for the data analyzers. 1st first, we need to think upon, uh, uh, how you approach the data. Now the data would be in the form of Excel sheet, the data in the form of text JSON format, the data in the form of text format. We need to understand how the data approaches and how you analyze the data and how the data should be, uh, more flexible into your architecture level than we drive the software component. So you need to aware each and everything when you validate your accuracy. Now data accuracy, when I say that can be, uh, not come in a standard single day. It means that it has to be mature over time, and it means that so you need to do more and more, uh, way of testing more and more business drive into it so that your software accuracy of your data will be scaled upon.

Have you worked with Weave API? These are template and discovery in building web page. Yeah. Uh, good. Uh, Web API is mainly used, uh, Web API is mainly used for an application interface for the service based content when you totally depend upon to fetch the database on this server side. So it is an interaction between your application and your software concern. Now the software concern may be the API is it's an application programming interface that can be drive in 3 areas, which now it is 5, but it is mainly in 3 areas, webs, Windows or, uh, web Windows, mobile, IoT, and cloud, uh, cloud based application. So there these are the 5 areas that you have you worked. And when you say about razor template, now razor template is mainly used. It's like a a higher version of HTML content. Or you can say a dynamic content generation where you can drive your code multiple label Excel means in that you have to write your HTML content. You can inherit the JavaScript or jQuery packages. At the same time, you have been using your runtime c sharp or vv.netcode when you will use the template with Razor. Now coming to your web API point, so web API is a Vivid, so where you can have your rest architecture principle that you have to be taken care of to develop your rest API while building a web API application. Now there are many tools out there which you make you more robust and scalable to doing to it. So it is totally up to you how you develop based on your business functionality, but this is the current scenario that you have to be involved upon your web API.

I think we didn't see So how will if we can pause it, we're going to use it for the I'm sorry. Hold on. Okay. Now coming back to your point on delegates and event. So delegate, I've been using in my, uh, banking and, uh, domain sector. So delegates is mainly used as a pointer based function when you have to generate value multiple time within the same object of same return. And let's take an example that you have an addition or you have an, uh, subtraction. So you have to instead of calling a method, you have to call that particular class method into your delicate property so that your run time environment, your final add to output might contain a multiple value. So this can be proposed with the help of an event. So even will use to notify that what particular action has to be performed, and that particular action performed with the help of delegates. So it's like a shaking hand join join with venue. Do perform even then delegates. Now a real time example when you say, uh, in terms of banking and finance sector, when you have a lump sum calculator. When I say a lump sum calculator, it means a mutual fund, then you have to perform. Uh, you have to put certain perform to check a particular stock or particular mutual fund for a 5 to a year, 10 year perspective. In that particular 5 to 10, when you generate the sequence of your, uh, deposited money or you're investing your money, then you will perform this kind of event or delegates. So I've been using in banking and financing sector. Now coming to the point of your interface over extract, it is a, uh, a subside of an interface. So abstract class is like a concrete and interface is mainly used to declare in the inherited class. So we mostly use inherited, which is morally, uh, comply this solid principle. Now coming back to your garbage collection, So, basically, we need to create a software that that that has to be utilized more memory management or garbage collection. So in in respect to your soft location, if your architecture is not good, so your memory management will not be cooked, which consume more and more memory on your server level, which make you hang at certain point of time. Your application will not able to perform more scalable and more robust. So garbage collection will use when we have to provide for any kind of connection that we need to be used, and we need to withdraw that connection itself or certain objects variable where we, uh, won't able to accept more and more for that. Then we can release that particular object to make the clear architecture of your garbage collection.

When would you choose abstract containing usable piece of code? Explain the pros of this study how to extract your code. So, basically, abstract code is mainly used act like an concrete. It is mainly used when you have your design pattern. So when you are developing in any kind of software, you're you have to implement in the in the form of if you have a product level application or ecommerce level application. So at that point at that particular point of time, you can be used as an abstract method where you can define Surtell method within your class, or you have to define that particular method, or you can define in the inherited class. And that's a particular approach is where you can use abstract method. So that would be more advisable. So coming back to your point in terms of reality, when you use that particular, you can use it in terms of ecommerce application will be the 1st advantage or any kind of financial based application you can do. So this, uh, this would be the approach for, uh, usability of your code.

It's like a situation when you took the initiative to solve a problem, but, basically, take your responsibility. What was the result? Okay. So there might be a situation. Like, when you say dotnet platform in dotnet platform, you might get, uh, multiple error, uh, at a certain point of time when you develop certain functionality which never works at that or maybe the functionality approach will not extend to that particular required network. You mean to say at that point of time, we need to take that approach. We need to take that initiative to see how the approach would be. Now even if it is an application concern, so we need to, uh, retest that for, uh, application even in the, uh, UAT session or any in the pre port session to check if the, uh, application that what we are getting error in the live environment so that we can replicate the same even if we, uh, need to check. The second thing, if it is into database level, then we need to replicate the same thing about we need to check. And the third thing, we need to check the network connectivity itself because if that might also get and create an issue when, uh, there's a high traffic application and you're, uh, able to see it. When when you see that the application reaches to it instead, then we need to see how that we can configure and how we can avoid that type of such an error in that particular note.

So what is the difference between view function and store procedure? Okay. So view is like a dynamic view is like a constant data. Data that can be updated or it's for a temporary basis or you can say you can modify view every day to day or every month to month basis. So that is view. It's, like, a a starting data. You can say, uh, in in spite of, uh, creating a heavy reliant on main table. A function is nothing but a small piece of code that can be executed. So real time environment, when I say function, you can use a small code of code that calculate any particular business logic. So that's and stored procedure is nothing but a series of executable statement. So you can drive a heavy, intense, uh, statement in terms of stored procedure function. Only we can write select, uh, select statement. But in store procedure, we can write data manipulation language kind of queries. And store procedure is mainly used to have high intense application. That's what I have been told earlier also.