As a seasoned software Developer and Software Engineer with 3+ years of experience, I possess a proven track record of delivering successful projects . My leadership has been pivotal in ensuring optimal project outcomes, consistently emphasizing quality and client satisfaction. Through technical proficiency and dedication, I have worked on multiple projects to successful completion. My commitment to excellence is evident in my approach to delivering projects at their best. Looking ahead, I am eager to contribute my expertise to future endeavors, continuing to thrive in the dynamic landscape of software Development.
Software Engineer L2
Compunnel DigitalSoftware Engineer
Kellton Tech SolutionsReact JS
Redux
Axios
Node.js
Material-UI
Git
Metamask
API
Hello. My name is. I did my graduation from College of Engineering, uh, in 2021, and currently, I'm working as a software engineer in computer, uh, located in Noida, uh, for past more than 2 years. And, uh, my tech stacks are React, HTML, c, and the JavaScript, Angular, and, uh, also just an enzyme, uh, uh, material. And, uh, I have worked on the when worked on the project, like, customer portal and anti money laundering systems. And, uh, and also the project, uh, based on the metaverse, like, uh, that uses web 3, I worked in that project in my previous company in. We have made a project for Ampol NFT. It's an NFT market in which we use a MetaMask integrated with the developer web 3 in React. And and, uh, I can all I I also work in Angular also. And, uh, currently, we are working on a project named antimony laundering system in which we have to in which we have to, uh, we have to take care of the transaction details of the user who is who is playing in the, uh, playing in the casinos to get them the, uh, to get the details so that no money can be laundered at the time of playing. And, uh, so we are handling their content from the React and Angular. From the currently, we are in React, uh, but this application is also built in Angular also. And, uh, we are maintaining it from the React side and Redux with the help of for the state management system. And, uh, and I'm eagerly eagerly waiting to, uh, waiting to uh, waiting to learn new technologies with the new, uh, with the new new phones like you. And, uh, I hope, uh, you will like this video, and, uh, I hope you will, uh, you'll understand what I have said.
When working with Next. Js. Next is how you decide. And to use use static. Use static versus server. Okay. Uh, in next years, we can static generation data fetching user gets state. So browser when you fetch the data at the build, uh, build build run time, when we fetch the data from the build time, we can use static generation s g. And, uh, this deal with the context that does not change frequently frequently, such as marketing page blocks, post documentation generated with the s t one can be saved in the static generation without data fetching. On server side rendering, we can use get service side props when you need to fetch data at the request time. When we need to fetch data at the request time, we use server side rendering. And when we need, uh, phase the data at the build time, then we use, uh, static in this for the page.
In next years, how to handle client side navigation navigation of the pages that require refreshing. We can, uh, we can do we can handle client side. We can be very into performance, scale and use the pre prefetching. Uh, we can use the link link component with the prefetching. Uh, when the link component in Next. Js prefetch the link, uh, page by default when it appears to the viewer. Manual prefetching Manual prefetching, we can use useEffect hook to the router dot prefetch with the helper of router dot prefetch. And we can use custom navigation prefetch also. For more complex scenario, we can use prefetch multiple pages. You can extra access with the help of custom navigation. Custom navigation because of them, uh, prefetching delay. So link component with its default prefetching behavior is often sufficient for many application. Link is the often we use every day.
Strategy to implement responsive design using CSS. We can, uh, we can use fluid grids. Uh, grid is at, uh, 12 ways system. Uh, low and column both, We can use a grid fluid layout can help us to make a responsive, uh, design, uh, based on the resize proportion, what we need. And flexible flexible images also, we can we can give and show image cycle and, uh, their height is we can make it auto. Media queries, we can also write. We can note media colors according to the space size and conditionally based on the viewport and other characteristics also. And typography, we use specific thing. And to that, you use alternative units like EM and REM for, uh, font sizes, padding, and margins to ensure they scale properly. We can use that also. Or Flexbox musicals, the flexible powerful layout without without it allow you to line on the, uh, allow and distribute space on the item in the container. We can use grid, but, basically, the main thing is grid. And responsive navigation, we wanna have to if we are strategy to make a, uh, responsive design firstly.
Method who do you employ to centralize API call? Method to employ. Send from API calls. We can use Exuse. Exuse is the basic library that we can use for, uh, for centralized application. We can directly install the Exios library from Exios, and we can make a base URL, uh, at the URL dot g s page, and we can make a base URL where we can set a time out and headers also so we can use that anywhere in our application login page. If you have the component, you can also like, example, if we have make a component, we can fetch this directly to pass the URL. Also, we can create a, uh, customer to fetch the data from the API with the help of, uh, with the help of Exos. Error handling in the because error handling is very, uh, commonly preferable in, uh, Exos rather than any other method.
SEO, the Tractic, sodium flow, enhanced application load time. We can enhance it. Static generation use. Static generation is optimized image image optimized. We can use Code splitting is the main thing to, uh, made our application application faster and the credentialing caching and CDM get server side optimizing CSS lazy loading There are many method to do that.
In the typescript function, please explain what might go wrong if we don't properly validate the input parameter. ID user is equal to function. Imagine this will be sent back to our back end. It will it will it will throw an error because if, uh, if the data or the user that we are that we are passing to function, say user data, like, it is an object containing ID and if that it doesn't doesn't pass a user type to a data that we are, uh, we are basically default argument we have set. To then it doesn't understand what type of data it is coming. But currently, we have initialized the u in initialized the type of the user that is that is containing ID. ID number ID is a number. Name is a string. So it's an object. So it knows the data will know that we I am receiving an object that we need to send in a API. But, uh, what if it will go wrong, it doesn't if it doesn't describe what type of interface we are creating for the data object, it will throw an error that it is not understanding. Reference error, it will throw.
That is a tailwind CSS in pinpoint In point, the potential issue, whatever I do. I'm just trying to find and restart. We can performance issue can do. We can't rerender if there is a change in CSS dynamics. In this compact, uh, complexity, increases, uh, debugging difficulty and limited CSS feature.
I will I will I will I will make a custom hook file and, uh, with the help of you, uh, use, fetch, anything, uh, create a file, and we will use the state management, uh, use state where we can set the data, uh, return set data function. And with the help of that, I will get a URL from a parent component that is using the customer. When the customer received the URL, that will directly go API with the base you API with the given URL. And, uh, with the help of SEO, we can directly access the data and also, uh, try to also handle that with the help of try catch. And, uh, that introduced data. We can do that with the help of a try catch. We can catch the return and return that, uh, in response to any component that they're using that custom.
Leverage, we can Over call quality. LePage, we can do types we have to set in the next years to provide building support, and, also, its leverage is, uh, we can say that significant enhanced code quality by providing static type checking. It will directly, uh, check the type without even in the compile time. Better tooling about that improved developer experience. These are the things that will help.
I will take, uh, the consideration that, uh, that API API give the proper error hand, proper error status, and, uh, proper error messages so the user the third party user that is accessing the type a that doesn't get, uh, get confused what type of response is giving and also that response should be come in a valid JSON. So we can directly map that response to use it and send it anywhere. These are the considers that we take implementing API.