Sivadutta Panigrahi

Hi. I'm. I have around 15 years of solid experience into various Microsoft technologies. I've started working as a dot net engineer. Right now, I'm working on dotnet technology as well as SharePoint and, uh, Power BI, also part of my daily routine activities. I do manage a team of 5 people who works on various technologies, like, uh, some people are working on Powerbase, some people are on dot net, and I do manage them. I do design, uh, the software for them, design the solution for them, and I do code review. That is my daily to daily basis work. Uh, in the personal front, after then, I used to prepare all the reports and, uh, give my updates to my peers who sits, uh, at a different, uh, part of India. And I usually keep myself updated by reading blogs and searching new new innovation videos as well as attending Microsoft talk shows. Okay. During my spare time, I used to play cricket and football. Uh, I'm very much religious in my belief, and I do work a lot. I strictly follow my guidelines. I usually start preferring a daily basis, uh, stricter timeline working routine as well as giving the extra time to my well-being as well as to my family. Thank you.

The accuracy and the reliability of the data depends upon what is the requirement and, uh, what the customer need, uh, the output as a output, whether it is a web page or whether it is a reports or any findings from our code. Then accordingly, we can design the solution. If it is a dot net based application, then we have to use the, uh, we have to use, uh, uh, these design principles or GoF principle, which will help us to build a great successful product. Apart from that, we have to implement a test, uh, driven approach, and we have to, uh, like, also decorate our classes and the structures, everything in a summary so that the following, uh, parties, the peers who review the code or the juniors who are following the classes and structure, they will follow the same routine and proceeded, uh, further. And if I find any, uh, concerns on the data accuracy or any bug findings we do I do make. Then all these things, we I used to, uh, discuss with my teammates before presenting at them, like, uh, this, uh, can be how it can be avoided and what are the best principle or guidelines, uh, which is, uh, recorded by Microsoft can be implemented to overcome the, uh, stress of data as well as, uh, make the program error free. To validate, we have lot of, uh, uh, like, tools and, like, FX scope. All these tools are available. Those tools, we can implement further. Thank you.

Hello? Yeah. Can you please call me? I'm in a interview. Can you please call me after 30 minutes? Yeah. Thank you. So responsibility comes from the designation, not from the work atmosphere. Many time, we feel that there is another team who are might be like, a classic example if I'm giving for a classic, uh, scenario. There might be something who are actually handling the DevOps, okay, who might be, like, uploading the documents into Git repository as well as checking them, then, uh, making the CICD pipelines. So this is not part of the delete to delete versus routine of a developer who works on the coding front, or let's say, if the coding front are best support, uh, this dot net technology. So as a engineer, we know how to work, how to resolve the issues in, uh, GitHub. So I usually walk up to them and try to understand to find the error is coming. Whether that is coming due to the network related issues or any coding related issues might also, you know, quite happening. That is possible. So I used to support them a lot for DevOps processes. Apart from that, we have dedicated, uh, team to maintain our database. But as a developer also, I know very well, uh, you know, SQL Server, how to write queries, store procedure, and the triggers. So there also, I used to, uh, like, uh, give them advice to modify their queries. And this actually produce a great team bonding as well as the project overall project or maybe if it is a separate project. The, uh, vertical, I mean to say, is that the whole vertical who comes under a single uh, project manager responsibility, that becomes a successful, uh, like, goal achiever. So that gives a tremendous pleasure to me to achieve the greatest satisfaction from the, uh, client side and from the peers. Thank you.

Yeah. So for the projects, filler, uh, depends upon the various criteria and the various factors, which may be due to, uh, like, a lack of understanding of, uh, like, a requirement and giving the proper feedback beforehand to the client or before it to the, um, responsible person while they're running into these problems. So all these, uh, uh, like, factors or deals, uh, like, give a tremendous opportunity to learn from the mistakes as well as prepare for the best result. So to overcome the, uh, this project failure, uh, so it's a better, uh, because I'm a a software architect. So I hold maximum responsibility of my team's working, uh, styles or less the, uh, product which we produce. That becomes my responsibility. So, usually, I do not transfer the negative feedbacks or the if there is any negative flags coming up from the top, I do not transfer it to the subordinates because, uh, these guys work under me. So I take full responsibility if there are any bugs found of or the project or the, uh, product which we developed is not working or giving the utmost satisfaction to the client. Then, uh, I'll try my level best to, uh, like, adjust down the errors or adjust down the bugs or adjust down the problems which we are facing right now and what we could have done better for that project particular project so that these things could be available because of our nature of working is agile. Right now, we are able to manage at least more than 90% of, uh, perfection into our many of the projects. So there is absolutely no problem. But, yes, there will be certain cases where depending upon the customer's, uh, establishment or the their, uh, like, infra usage, we may pass we are still facing some of the issues, and we'll we are overcome overcoming those issues by adjusting our practices or course depending upon the situations and demands. Thank you.

Yeah, web API is nothing but if I can tell a single responsibility principle, if I have designed and created a service, okay, and deployed it into Azure that became a web API. So these are like a simple getter-setter method or like we used to call any function to get some of the results as well as if we want to post some data to the database. So that time we use web API mostly, like all about crowd operations, like create, delete as well as update and delete. This time we can create these web APIs which can be free floated and it can support to many like calling clients. The calling client may be a mobile phone application, may be a web page application, and maybe some other applications. It depends, it does not depend upon who the caller is, but it actually understand what the caller wants and it will response accordingly, whether to edit a record, whether to give just a give a value or update a record and supply back the result. That's it. Yeah. So in web pages, if we have used our MVC controls or if we are using any REST API call, that become actually like useful in calling this web API. Result templates are nothing but these are the inbuilt architecture, inbuilt templates so that our, this HTML and the body styles can be grouped together in a ASP.NET based applications. Thank you.

Yeah. Events are nothing worth of which occurs if, uh, for an action, like, if we are, uh, pressing a button or, uh, after that version, uh, after that button pressed, uh, what is the outcome? So those are called edge events. It's a catcher of, uh, like, in controller. We make these events available as well as catching the, uh, front end actions and, uh, process it further in C sub best applications. Okay? Like button click event as well as, uh, this blur event or mouse out, mouse in, key in. These are the different type of events available in SP.net CSR based projects. Okay. Uh, interface over in abstract class. Okay. Here in there are the basic difference between interface and over, uh, abstract class means interface can contain the method signature only. And, uh, if any, uh, class or child class is, uh, using interface, okay, then we have to override it and do our own implementation whatever way we like it. Okay? But we have to implement all the, uh, uh, like, methods if we are using a interface based class. But in case of our star class, all the methods should be abstract in nature, like, uh, a void we can use. Okay? And, uh, in the calling class, the child class, we have to overload it. Like, if it there is any, uh, like, a plus or minus calculation is there in the abstract class, then we can override it, overload it, and, uh, create a, like, subtraction or multiplication in my child class. That's why it is basically, uh, abstract in nature in the base class, and it can be overloaded easily or overwritten easily in the child class. Garbage collection happens automatically in c sharp program. So the basic, uh, like, situation comes is that whenever any collection string is opened, uh, then it has to be collected automatically. That's why we are, uh, following trial case and finally. In the finally block, uh, we can see if a connection is still open, we can just dispose the connection. Those becomes, uh, like, uh, collected by the garbage collection mechanism. And it actually runs through the generations. Generation 1, 2, 3, and 0. Okay? So we may not have to explicitly, uh, call the garbage collector. It can happen automatically. Thank you.

Views are, uh, nothing but a virtual representation of tables. Uh, it's basically used for database purposes in SQL Server. And these views can contain multiple select queries, though we can update the views from the front end. But it is advisable not to use complex speech or complex, uh, statement to create views. In those type of views, it will be very much hard or it won't actually update the records that is available. The functions functions are nothing but, uh, there are so many inbuilt functions like max, min, greater than, equal to, less than. Those are the inbuilt functions available in SQL Server. And we can create our own functions also. Stored procedure prebuilt select queries, which are, uh, actually, we, uh, program stored procedure so that, uh, these are pre compiled. And we can use this stored procedure, uh, and pass parameters. So accordingly, the parameters pass passed to the database, it will perform the select, insert, or update, uh, operations in the database, and it will be, uh, giving best as the result. Stored procedures are definitely faster in comparison to the user functions because those are pre compiled. Those are already compiled. So it, uh, the calling program does not need to rerun the functions or these, uh, select statement each and every time. It will just, uh, gets hold of the test output is passed the parameter, use those, uh, parameter passed values into the select or, uh, other queries, then give us the results. Thank you.

For web applications, it's very very much necessary to understand, uh, like, whether, uh, to use, uh, single page applications or multiple page application. And, uh, depending upon that, we can, uh, like, create application either, uh, taking into consideration of these, uh, licensing cost and everything either as a .netcoreorplainsp.net MVC based applications. Okay. Depending upon the resource availability. Accordingly, we have to also create our solution designing by using MVC principle. Okay. Or dotnet. Any, uh, like, a blazer based or blazer pages we can use depending upon our requirement. And, uh, we can present the code or we can present the web page in a beautiful manner. Apart from that, we need to also take care of the database connections and the related, uh, database, uh, where it is and how to maintain these connections and how to produce, uh, the results in the web page itself. Whether that is a plain, uh, uh, cycle, uh, like web page or a crawler presence are going to be performed for this web application. So we have to think logically on that. Apart from that, there is another aspect of it. We need to, uh, maintain the modularity of all the web applications. So it can be, like, auto resizable based upon the tablet uses or, uh, our laptop uses. So it's basically, we need to, uh, use Bootstrap and CSS so that and, uh, like, a jQuery based app, uh, like, uh, JavaScript implementations. So and dependency injections, this modularity, and everything, and our routing mechanism. There are so many aspect of it. Once we get the project idea, we can, uh, create accordingly our web applications.

Okay. Uh, to choose the abstract functionality means I do not know what the calling, uh, function will be, uh, used, or I do not care about the caller. In that case, I'll create a, uh, like, abstract function or abstract class. So that my calling function can decide how to overload it and what to be needed from this abstract functionality. That way, we can implement abstract, uh, classes into our code or into our project. And if I deciding upon the approach means, uh, we have to make it, like, uh, a void so that it will be, like, easily, uh, accessible by the calling function or the child class. And this child class, uh, can implement, uh, throughout the code structure. And it has to be, like, implemented throughout the classes so that everybody follows or all the class follows the same basic principle, and it will have the a test driven approach. The code modularity will be applied beautifully here, and we can, uh, like, uh, troubleshoot the errors. And if we can change if we want to change any of the signature, then we just have to change in the abstract class itself, then the following code will be automatically updated. In those type of cases, after class is much more useful.