Narendra Maurya

So myself, Nari Moore, I'm a full stack software developer. Have been working in the industry from last 5 years, and I have hands on experience with the React JS, Node Express, MongoDB, Laravel framework, as well as React Native, Ionic applications, as well as have some hands on skills with the c plus plus as well as Arduino programming, like, uh, user and creation, like handling the pin setup for the microcontrollers. So those are the things. And currently, I've been working as a free as a, like, a side project, which I have been developing for the factories to help appliances using Arduino. Along with that, I am a full stack software developer as, uh, and as well as a programming instructor on YouTube channel, which is the codebook inc, where I used to teach the programming, but due to some job constraints, I couldn't go do that much. But right now, I've been doing good with my current company. So right now, I wanted to switch, and that's why I'm here. So I have, like, hands on experience with vj Vue JS, React JS, Next JS, Remix JS framework using weird applications also. I have created several of them. Node Express, Fastify, MongoDB, PostgreSQL. So that's my that's a bit intro about me.

Okay. Okay. You use this to clean code clean code transfers to improve this code. So if x is less than 0, say, if any negative number is there or or if it is greater than 12, then alert should be thrown there with error and return. Otherwise, if the x equal to 12, then it should give you x plus 1. 1. Otherwise, x plus 1. I feel this code is quite optimized. I feel so. But if you want to make it more cleaner instead of using ternary operators, we can make the use of if conditions, but I feel this code is quite quite good. So we are good with this.

Below is a function to calculate the total amount paid at table in the restaurant. There's a 12% VAT on the total bill. Which is a constant for all meals and additional tip is how would you use clean core principles to improve this function? Additionally, how would you modify this function so that it would be used across different tables? What are different restaurants? Const b person 1 amount, person 2 amount, percent tax percent, and tip. So we can define a constant for the tax percentage, which is, like, 12%. We can define that. As well as instead of passing all the arguments, like, uh, percent one amount, percent two amount, we can make the use of a array where we put let's just pass the values of the array as a bill all the bills of each person as an array and just pass in that. As well as a tip is fine. So whatever that tip is. So from the from the from the arguments of this function, we can get rid of the person amount, percent 2 amount, percent 3. And we can make the use of create use function in order to begin the sum of the total bill that has been passed as an array in it. Uh, We can make these a constant that we have declared outside of the function, that that is tax percentage in order to calculate the tax, as well as then add the tip and then return the final bill to that. So that would be my approach in order to make this function look more cleaner. And in addition to that, we can add more safety checks, like, if it is empty, uh, area has been passed or something like that. So it would handle that. Even in order to handle, like, any like, random arguments have been passed into into that, we can make the proper checks for that. And along with that, we can also use TypeScript in order to define the arguments that has been passed just to validate them. So that would be my approach to do that.

So use effect is a effect that we want to get in our component, uh, when the component is mounted or have based on it, any certain dependency. So we can make the use of useEffect. UseFocusEffect is, like, uh, I'm not that much sure about it, but I haven't as I haven't used that much, but use layout effect is something which, uh, which runs when the DOM has been completely painted with the, uh, the initial phase that comes on the so we can create some kind of, uh, action if you want to perform that so we can make the use of use layout effect.

Your company wants to launch a fitness app in 6 months using as a lead developer. How would you create the project timeline, ensuring all the features such as sign up working, workout tracking, and the social sharing deliver highly I like the matrices such as sprint length, team size, and critical milestone. So my approach here will be, like, uh, using agile methodology where we'll break down all the features and their flows and get their flows into a place, like, uh, what will be the flows of from when when we move from the sign up. So in the first case, we'll initialize we will do that. Then we'll start creating the layouts of them, uh, along with some sort of functionality. And later, we we'll keep on binding with the applications. Uh, not the applications. I would say rest APIs, so which will record all sort of data and making get get calls and post calls, as well as having, like, uh, we can make the use of redux saga or redux thunk in order to manage the state of the application. For for example, we have authentication state of the application where we can find any user is logged in or not, which is globally shared. And along with that, if you want to if we don't want to use any kind of a side library like this, then we can use built in reuse context hook just to create context and provide that whole state into the application, which can be accessed at any point of time. So that is one thing. Handling all the APIs, we we can we can make the use of a third party API calling library like Axios, which is very very decent in order to and comes up with a lot of things. As well as we will define some constant where we will just add all the constant, uh, or, like, a make based on the build, we can just create some kind of a ENV file, which from where our constants will be. So everything will be in its place. For example, API based URLs can be a constant. Some of the other thing like region and whatever the based on the requirement, we can make the use of the constants. Then we can define all the components and their layouts using some kind of a like, if you want to speed up that, so then we'll look for some kind of a third party UI library, which is already available and solves our problem. For example, for just to show the key matrices, we can we'll we'll analyze which which charting library that we can use in order to achieve that there. So that will be my approach, and we'll go through the documentation of that library that we are going to use in. In order to make the UI more seamless and more performant, we can go through the documentation and make the things and we can make the things a bit easier for us. And also what we'll do what I'll do, my approach will be, like, uh, just focusing on the flows and catching the errors and our loggers and creating a separate API endpoint in the back end where we can just log all sort of errors where we are facing so that in order to in order to rectify them in future purposes so our app doesn't break. So that would be my approach.

So in order to make our rerendering much more efficient in where we are using, uh, uh, like, expensive heavy competition where we are heavy using some kind of a database based on that. So I'll use use memo so that our React application each time every rerender doesn't break that, making the use of using predictive handler handler as well as forward graph in order to, um, make the state as local as much possible so that it doesn't make it doesn't force the main component to rerender itself again and again. And optimizing them will be, uh, I have already worked with several applications where I have tried optimizing. Like, I have implemented caching so that it doesn't go through the API calls most of the time. Using function caching that, like, where we pass the arguments and we cache them and the results if the results are gonna be constant. So we'll make the use of that too so that our our functions are not called more frequently. Instead instead of that, it will give the give the cash results. If it is if it is its results are not gonna be, uh, like, uh, are not depending. It will be like, it depends on just the arguments. So that is one more thing. Making the use of, uh, less use of use state and those things in order to make the make the React app, uh, React component to rerender itself again and again, avoiding those kind of things. For example, using use reducer hooks where we have a lot of state to manage, and we can make the use of user reducer hook just to optimize them and just to uh, prevent the state changes frequent state changes. So that would be my approach as well as, uh, as well as also using API, uh, for for manage less is for less use of use try I will use less I'll use third party library called 10 stack React Query in order to make API calls on the component loads, use mutation functions in order to make the things more seamless. And whenever we require, then it will call it. So that will be my approach here. And along with that, yeah, that's it from my end so far for this one. So, yeah, my plus point is, like, using dynamic tag react query, So which which I have implemented in several other projects where it has given better far edge over the things.