B Sai Uttej

My name is. I'm from Hyderabad. I work as a full-stack developer. I worked as a team lead for one and a half years, and I have a total experience of two and a half years. I usually work on back-end development, and I know the use of frameworks such as NestJS and NodeJS. And I have also worked with a variety of architectures like microservices and monolithic. For front-end development, I work with React, even though I didn't go with full-time React. But I usually build small applications and make small changes accordingly.

To secure my Node.js APIs, I would first implement a few steps, such as IP restrictions, and also keep a restriction on the number of API requests coming from a single IP per second.

I can use the window object which will be provided normally in React, I mean, say, in web development with which I can write a small component use size with which I can.

Yeah. If the given function would like to count the elements in the list, but there is an condition which is only incrementing the count value if it is 4. So, if I remove the if condition and get through loop, I can get the print of I can print the length of the list.

But we can manage the state of the object using local storage in the frontend. We can use voice, what we can see? Caching the request, I mean, say, using cookies to store the session. Usually, we can implement two types of sessions, either using JWT or session-wise things. While when you're using JWT, we can send the JWT, or we can store the token in local storage and send it for every API request, making the backend use it via headers. While for using session-related things, I mean, say, we can use cookies. So, the backend will only create the cookies, and the cookie will be passed for every request of the frontend application.

Well, Redux is actually good state management in React, but it becomes quite complex to manage the state within as our application grows. However, its alternatives are there, and we can use signals or other things. State will still be there. I mostly use Redux when I'm working with a small PSTL, I mean, there are not a lot of states and I just need to update the state for particular pages.

Well, there is a variable called name in this function, which is, if it is not still declared, then it did not declare anyway the function. Either it should be passed as a parameter, I think. If it is passing as a parameter, then it can be fixed. I mean, if input to the function is name, then it can be fixed because the name variable is not declared anywhere. While function calling is actually passing that name value, but it is not declared in function definition. I mean, input to the function is not declared. If we add name in the function declaration, then the problem can be solved.

Well, syntax itself is wrong, actually. The for loop doesn't have an end condition and also is not incrementing i. So, if we write a normal full loop with "for int i equal to 0 comma i less than items dot size col," then i plus inside the function, we can write "items of i equals to items of i into 2." Then it will double the values of the.

Well, when we're writing unit tests for React components, actually, we'll try mostly to manage the state through props and also try to implement mocks for their respective side effects related things.

Well, I'll use GraphQL or REST in my project. If the response of the object is a lot, I mean, say, it's quite complex, and I only need some part of the response itself, then I can use GraphQL to structure the response so that I only get what I need, not to get all the related things.

Well, I can use lazy loading in React to improve the loading time of pages, which is actually supported in React by default.