
I am Nitin, 26 years old and currently working as a Frontend Developer. with 5+ years of work
experience. Strong communication, Interpersonal, kinaesthetic and analytical skills. Highly creative
and eager to learn. A willing worker who is flexible in a cross section of working environments and
possesses remarkable team management skills.
Senior Frontend Developer
HESTABIT PVT. LTD.Frontend UI Developer
ESHOPBOX PVT. LTD.Jr. Frontend UI Developer
GINGER WEBS PVT. LTD.
Zaplin
Figma

Git

SVN
.png)
Jenkins

CMS
Hi. My name is Nathan, and I'm a front end UI developer, front end developer. And I have 3 years experience in React and Next Years, and, uh, I'm currently working with. Previously, I was working with EshopBox as a front end developer. And, uh, my roles and responsibilities are here. I am basically as far as the front end of the application, and I've led 2 projects of 5 people. And currently, there are 4 people under me. I
We can have multiple, uh, feature, uh, branches, like, uh, for version like for March and March 2024 to get the, uh, updated versions. Like, uh, they, uh, uh, there will be no more, uh, repetition of course, like, if we use, uh, separate branches for each and every month so that, uh, after couple of month, it, uh, gets tracked, like, uh, what is the updated branch. We don't have to hustle around.
Okay. So, uh, in terms of project hierarchy component hierarchy, I'll be separating all the components, like, uh, components, pages, and all the, uh, dynamic components so that each and every, uh, code is, uh, separated into, uh, multipaths so that they'll, uh, only those components update, uh, which, uh, needs to be updated, not whole page because it will, uh, affect the, uh, speed of the project. So that's why, like, uh, I've developed dynamic components for, uh, charts and, uh, sidebar and main page layout. So, yeah, I'll those, and, uh, that will also increase the reusability of the code because we don't have to create each and every component every time if we want to work with.
Okay. We will, uh, act first of all, I'll use use state to see if, uh, the code is updating, uh, rendering correctly. Afterwards, I'll check, uh, uh, bypassing the dependencies if the components update or not or the states or which is affecting. And afterwards, I'll correct those method with help of your use ReactOS.
Okay. So I'll be using, uh, restful APIs, uh, by having async COVID. Uh, by that, uh, if there if there, uh, has been an error, it will throw an error. And let me know what is the what is the cause, uh, of that, uh, error, and I'll rectify it.
Yeah. Uh, the state is currently updating twice. So if we want the increment of 2, so we should write only set counter brackets parent, uh, counter plus 1. In place of 1, we can use 2. If you want to update the, uh, count by 2. If the if you just want the, uh, upgradation just by 1, we can use counter plus 1 or just plus plus 1. In case just, uh, one value is updating, the React will all, uh, on update it on its own.
So would you follow to the diva and our data storage? Uh, I will create multiple, multiple, uh, reduces and for each and every component so that the code is, uh, understoodable and multiple actions and so that each and every action, uh, is understoodable, and the other developer can work on it easily.