Nilesh Jadhav

Uh, Hi. Myself, Nilesh Nilesh, and I'm from Kolhapur, Maharashtra. I have completed my bachelor's in engineering from, uh, Shivaji University, Kolapur. Currently, I'm holding a 6 years of experience, including, uh, back end and front end as well as a cloud services. So in back end, I work with the, uh, dotnetframework, dotnetcore, uh, using c sharp as a programming language. And for front end, uh, I'm working with the Angular along with the, uh, HTML, CSS, JavaScript, jQuery. For cloud, I can work with the Azure or AWS both. And for databases, I am having experience with the SQL and PostgreSQL. And, uh, for data representation, I can work with the Power BI also. So my overall experience is a 6 and a half years. Uh, project till I worked, uh, now, uh, mostly related to IoT domain, educational domain, and, uh, there are some government agencies which are holding the case documents. That kind of, uh, stuff I was working till now. Uh, in brief project, like, uh, we are reading the data from remote devices and getting the data from remote devices using IoT hub or IoT core in context of AWS. But I will more, uh, focus on, uh, edge at your, uh, for this now. Uh, so, uh, in IoT hub, when we get the data, uh, we'll, uh, using the topic trigger, we'll get that data, and, uh, data may be in any format kind of, uh, hexamer, uh, binary, or, uh, decimal. So I have to understand the data correctly, which format it is, and I have to extract that data into proper format, maybe decimal it is. And I have to store that data into the storage table. Uh, and from that storage table, we are performing the but, uh, how we are reading that data? We are using the Azure function. For that function, we are having a topic trigger, uh, using service bus mechanism we are doing. And once we get that data, we are, uh, extract that data, save that data in Azure storage, and then, uh, we have some algorithms, uh, which will run frequently. And, uh, on that data, we are performing some aggregation. And based on that data, we are analyzing the device states currently what device, uh, is, uh, doing now, whether it is, uh, working correctly or efficiently, or there is some fault. So I will analyze that data, uh, during, uh, that process and generate, uh, the ticket if there is any fault. And based on that ticket, we'll create a ticket alert, and we'll auto assign the technician for that ticket based on the client requirement, like, uh, whether it is a nearest geolocation of that, uh, technician or available, uh, inventory with the tech, uh, technical, uh, person or, uh, skills and expertise of that person. Based on that, we'll assign that ticket, and, uh, throughout the journey of the technician, we'll track the, uh, details, like what, uh, he, uh, done, uh, to resolve that ticket, how what inventory use, and, uh, some other stuffs we are also may maintaining as a inventory purpose. So that is my, basically, first project. Uh, second one is a educational domain where we are maintaining the student, uh, uh, associate and center, uh, information, like, taking exam and that stuffs. So that is, uh, all about me for now. Thank you.

Uh, during my last project, I was working with Azure Media Services, where we have to integrate the audio or video, uh, kind of services from Azure, and we had to show that, uh, streaming to the end user. But we are unaware about that how, uh, should we do, and there are less people and, uh, less documentation on that. So I re research bit, uh, more on that, and I take the initiative, uh, that is my not responsibility. But, uh, once once I assign, uh, for that project, I I am doing some R and D on that, and I've, uh, found that one solution, which is player, which will, uh, kind of, um, uh, JavaScript library, which will get the streaming from that Azure media services using some, uh, DRM token because security is must. And, uh, using that DRM token, we are reading that, uh, streams onto the browser. We have Angular application, and within that Angular application, we have integrated the that player. And from back end, uh, APIs, uh, which is dotnet APIs, which will, uh, connected with the Azure Media Services using some credentials, uh, which will from, uh, it will get some the, uh, access, uh, using that credential. The credentials are stored onto the keyboard. And from that, we are establishing the connection, and we are reading the data, uh, for the checkup player. And, uh, we we hopefully, we are successfully completed that, uh, application, uh, which is, uh, for Avanade, which is the Microsoft and, uh, essential, uh, partnership. And that is the first, uh, widely adopted solution, uh, from Azure, uh, which is, uh, my Azure media services. In that, uh, scope I mean, in that, uh, amount of, uh, like, users or request are are not handled by any other, uh, places, uh, that we have done. And my initiative is, like, uh, I have to create a transformation of that assets might, uh, might because, uh, the data may be in any format, m p 4, 3 g p, or SD, whatever. But, uh, we have to create a common solution where we have to, uh, efficiently steam that videos for end user and that I have completed using share cup player and doing the bit research on Azure Media Services. Uh, so that is working correctly now for AQ, uh, that, uh, one of the leading, uh, educational

Okay. So, basically, views are the virtual tables. We can say, uh, uh, the views are virtual tables. Like, uh, we can select on that. Uh, we can perform the select queries on views, but we can't perform any update operation on view. Function is nothing but the, uh, we can say it is a programmatical block where we can do some, uh, programmatical, uh, coding over there. Like, uh, we have a conditional statement if else or something. Uh, we have to iterate kind of loops. So we can do in functions. And from store procedure, we can call a functions, but, uh, in functions, we from function, we can't call a store procedure. So so in store procedure, we can say it is a set of SQL statement, which will execute, uh, as a group or a block. And from a store procedure, we can call the functions. But from functions, we can't call the store procedure. So function is a kind of appeal skill kind of, uh, thing. And, uh, store procedure is a kind of pure sequel, uh, thing where we have a set of, uh, statement within that. Using EXE statement, we can write the, uh, we can give the function name. Uh, we can give the store procedure name. If there is a parameter we have to pass, then we can execute that store procedure. So, basically, that is, uh, nothing but the store procedures. Thank you.

Okay. When we have our data accuracy and reliability, we we might found some, uh, differentiation or something. Data analysis. Okay. So, uh, we'll try to validate the source source data. Okay. Whatever we have in a source, uh, when we are pry presenting the analysis, uh, we'll check the source, uh, of data, whether it is correct with the, uh, target system or where we're having that data, uh, located. Like, suppose we have an n number of devices or, uh, data nodes, uh, from where we are getting that data. So we'll must validate that that data from a source of that data with, uh, where the data is presently current, uh, available. So we must check the source of data, whether it is matching with our, uh, source and destination of data. Like, destination, it it means, uh, where we are storing that data. Like, when we we we we are having a data warehouse, we must check that what data we are getting from source system, uh, whether it is correct with that. So we can manually analyze that data, or we can get some tools, uh, analyzing tools, uh, to analyze that data. So so using that, we can, uh, check the data accuracy and reliability. Other, we can create, uh, some sample mock applications or utility where we we will care care create the, uh, kind of test cases format, uh, logic. Uh, so we are mocking that data. Like, we are feel for, uh, uh, checking with the false and, uh, uh, positive scenarios. Like, uh, like, uh, we can create a unit test cases on that data. We'll check the reliability and accuracy of that data. Whatever we require, it is coming correctly or not. So we'll check the both positive and negative scenarios, uh, using some utility where we are providing the, uh, unit test cases on that data. And, also, we take care about the source of, uh, source, uh, where data is correctly with the, uh, where data is located. That's all about it. Thank you.

Okay. When, uh, uh, I'm working, uh, with the team or, uh, when I'm working as a team member, if there is something which is not, uh, meeting with the project guidelines or estimate or timelines, then I have to take the responsibility as a team member. Uh, like, uh, when we are pale, I am not saying. When we are lagging to maintain the project, uh, demands or, um, or application demands, uh, or customer demands, we can say, Then as as a team member, I have to take the responsibility or, uh, I have to initiate that we are, uh, all responsible for that, whatever we are making. So, uh, the when we are working as a team, we have to take, uh, the responsibility of the whatever outcomes of that project milestones, what we are, uh, expect to deliver. But, uh, due to some circumstances, uh, if we are getting some lag or difficulty to maintain that demands or requirements, then as a team member, I have to take the responsibility of of project failure or setbacks, whatever we are facing, uh, during our career phase or, uh, during our daily routine work. So, uh, when we are working as a team, as a individual member, we have to take the responsibility, whatever we are delivering or, uh, or whatever we are, uh, producing as a output of that work, what we are doing. So when, uh, team member, uh, uh, as a team member, we have to get the responsibility of what we, uh, uh, up entire team, what we are, uh, delivering, which is not, uh, meeting the project requirements or, uh, work requirements. Thank you.

Okay. Uh, when we are using the oops conserved and within that oops conserved, we have obstruction mechanism. And when we try to use the abstract functionality, then we can reuse the whatever code we are returning. So, uh, if there, uh, I will, uh, bit explain with the example. Suppose we are having a structured class, which are holding a method with we we can say describe product, and product is a abstract class. And, uh, within that, we have a describe, uh, describe product. Method is there, which is abstract method, and we can, uh, extend that, uh, abstract that, uh, in another class, we can say car. Okay? And so car can be any types. Uh, so within that abstract class, we we are having a properties, color, width, dimension, speed, RPM, whatever it is. Or in health care application, we can say we are having a, uh, abstract class, uh, monitor, which will monitor the health of current, uh, patients. Suppose the, uh, we can track the b b p BPM, uh, pulse rate, or we can say, uh, BMI, whatever it is. And each person can have a different range or output, uh, depend upon the person, uh, with height or whatever it is. So we can create abstract class, or we can create a monitor meter monitor person meter, which is abstract, and, uh, depend upon each person, we can display the different different result, uh, because we with each person having a deep a deep different range of, uh, uh, findings. Like, uh, one person can having sugar level 19, another person can having sugar level 120. So we are having all those properties, and based on, uh, that person will, uh, use that method to describe the, uh, their findings, like, whether it is a female or male. So all that, uh, this, uh, on monitor, we can display their specific information using monitor, uh, method. So we can extend the functionality of, uh, so we can say whatever we have to implement, uh, differently or we have some different different approaches to use, uh, but same, uh, prototype or name, then we can use abstract class or abstract method to reuse the functionality. Thank

Okay. So delegates is nothing but a kind of pointer functions where we are using to rep, uh, to, um, handle the events, uh, based mechanism or coding. Uh, like, it it is pointing to the function based on their references. So in that case, we can use the delegate. Events are nothing but the scenarios, uh, kind of same, uh, where we are, uh, we can say signal r is kind of, uh, if, uh, uh, when we are using a signal r, suppose there is something event at the back end. So we have to send that event to the front end, then we can use the signal out of our Firebase Firebase kind of things to the front end. So we can say that that is the event. Event is a scenario where, uh, using some conditions, the specific scenarios occurred, then we can say the event. So service was, uh, having a topic trigger trigger as a event. So even agreed having, uh, insert or update or delete event, that kind of events we can use for, uh, to invoke the audio function. And, uh, we are using same, uh, like, uh, what I mentioned, uh, like, uh, topic triggers and, uh, cue triggers we are using as a event on our project to run the functions. Uh, in, uh, when we have a multiple suppose we are having a a multi tenant application, and we have 2 2 methods, like, uh, multi tenant application and each tenant using different cloud. Suppose one is using Azure and one is using AWS. So then that time, we have created 2 2 repositories for Azure and AWS, and we have to common interface, uh, name like get a block a grid image, and, uh, we are having s 3 and blob. So over there, we have to, uh, register depend, uh, the classes depend upon a tie tenant, what tenant are you using as a cloud, AWS, and Azure. In that case, we can use the interfaces where we'll be deciding the which cloud should be used as a runtime. So where we can use the interface, so we don't have any, uh, like, during runtime, we have to implement something, then we'll use the interfaces. And nothing to, uh, define, then we can use the interfaces. And abstract class, when we have a partial, uh, implementation, uh, further we have to extend on our class, then we can use the abstract class. Garbage collection is nothing with the date resource cleaner, which can use arena.

So when during the, uh, implementation of something on a way back, we have to take care about the garbage collections that, uh, I hear on a previous, uh, case. We must implement the catching map mechanism. We must follow the best naming solution, uh, like, whatever you are defining, uh, should be clear and crystal clear for, uh, for, uh, another to understand. Also, we have to take care of data type. Suppose we are requiring something integer and we are assigned the law, so it is the best of memory. Uh, So and, uh, most probably try to create a async, uh, way, uh, use async of it where we're having the dependency on each other. So whether, uh, whenever required, just create a trace instead of keeping as a one by one execution. So it will, uh, execute the, uh, request fastly. Uh, use lazy loading, like, when we are using the, uh, use solid principle, we can say. So solid principle is nothing but, uh, make the single responsibility of each, uh, class or function, whatever you want. Just, uh, use that class for single response. No other complexity should be added. Or stand for open and close principle where we are, uh, using, uh, when we want to, uh, uh, add something, it should be open, and we when we are to modify something, it should be closed. So no, uh, other function should be hamper. Substitution of principle, it says that you should not, uh, uh, parent should not depend upon child's like, uh, each parent, uh, each parent child should be, uh, replaceable, or each child can replace their parent, and no other impacts on, uh, uh, remaining system should be happen. Uh, as as, uh, stands for, uh, interface segregation, we have to define, uh, we have to say that, uh, no user should be forced for implement, uh, that interface, which is not required, default dependency margin where we have to loosely support the system. So that's it. That is one of the best practices. Use catching, avoid deadlocks. So so use the locks, uh, to avoid the deadlocks. Use pagination whenever possible because it will, uh, significantly reduce the amount of time where from database to request. So that is some best practices, uh, to follow-up during the web applications. Thank you.