Manish Khedekar

Hello there. I'm Manish Kerekar from Pune, Maharashtra, India. I have eight plus years of experience in the industry, mostly doing web development and hybrid development. Initially, I started with AngularJS, uh, as a front end engineer. And from last six years, I'm doing React and React Native on the front end side. So, uh, I also do full stack development from last six plus years. So, combinedly, I have eight years of experience in web development, uh, and six years in the full stack development. So that's pretty much about me. Uh, as part of the domain, I can say that I have worked in the banking domain, telecommunication, health care, adjutant domain, uh, payroll solutions, POS solutions, uh, and algo trading, basically. So that's, uh, pretty much about me.

I want to be, uh, requirement of this, uh, new v six syntax and then the React, uh, React Native, uh, and, uh, most of the, uh, hybrid development part, uh, which aligns to my previous experience as well. Other than that, I have, like, uh, I have been part of product based organization and service organization both, and I have, like, I have worked in startup as well. So if I see the whole requirement, I think, uh, I can, uh, I am I can be the perfect, uh, match for this particular tool, uh, by considering my previous experience working as a React and React Native developer and then my expertise in, uh, advanced JavaScript and TypeScript. So I think that's why I'm good fit for the room.

So recently, uh, like, uh, I have built an application, uh, for my freelancing project. Uh, so, uh, we created a dating app. So, uh, like, doing that right swipe, left swipe, and then finding different profiles on the map and then sort, uh, like, uh, sorting them on basis of your, uh, distance from it and then switching between the, uh, tab navigator and stack navigator, and then switching between those pages, uh, with animations. And then, uh, other than that, basically, a whole, uh, uh, dating app, uh, like a Tinder or Twilio Madly. So that was the most impressive thing, I think, I can say, building React Native, like, uh, having by default support of Google Maps, uh, and Apple Map by integrating the map libraries within it. And then, uh, the other plug ins like camera and all. Uh, so we use the latest React Native. So, previously, it was having the React bridge within it, but, uh, uh, it got removed in the latest, uh, origin, uh, in Feb. So I think we have followed that one. So now it's more smoother. So that's, I think, the most impressive thing I have built recently in ReactID.

What's something technical you have changed your mind about? Yeah. So, like, uh, I like reading articles, and then I also write some article. I started writing articles on Medium. Uh, recently when, uh, like, people are doing AI from last, uh, two years, like, more than two plus years. And then, uh, like, as a developer, uh, there is a, uh, obviously, there will be a chance where you will think, like, uh, are you going to get replaced by AI or something like that? So, you know, like, when I actually started using these tools, uh, uh, it basically improved, uh, my coding abilities and, basically, like, uh, so instead so I got more time to think rather than to code. And then, like, if I do write a current, uh, correct prompt, then I'll be getting, uh, my whole code the way I want. So I think, uh, the perspective of AI I had two years ago is being changed in last year when I actually started using it for coding and other stuff. So if, uh, already I had told you the ex, uh, example of the previous dating app. So, yeah, the UI was there, and then I used that UI, uh, to create the layout from AI, and then I basically match, uh, by doing the, uh, layout style fixes with JavaScript in React Native. So I think that's uh, what I have changed. Uh, I would like what that's what the technical, uh, thing which changed in my mind in last year.

Okay. So I think, uh, most of the developer doesn't know how to document the code. So they got the task, they create it, and then they somehow created a PR. They get the review command, they fix it, and then they do same repetitive stuff, redundant stuff, uh, basically, again and again. And that's what cost time to company, cost time to developers, and cost time to team altogether. Uh, that can, uh, cost you delay in the project deliveries or feature deliveries. So, uh, I think, uh, uh, first of all, the way you should write a code should be documented somewhere in the project. If it is not documented, then by default, uh, at looking at any part of your code, you should be, uh, like, you should get the idea what kind of, uh, code quality is needed in this project. So that's one thing. Having the code documentation, uh, and writing, uh, like, developer should know how to write uh, a documentation for the code they have created. That's the, um, major thing, like, people don't, uh, think about. Other than that, whenever they review, uh, many people also don't know how to review a code. So I think, uh, like, uh, what kind of optimization can be done other than that, uh, like, how, uh, the current code is going to uh, affect the future outcomes of that particular feature. So that can also be, uh, done other than that deleted, uh, syntaxes of languages, which should be, uh, like, which should be learned or upgraded by these developers on, I think, uh, every semester or every, uh, few months. Why? Because, uh, the technology is changing drastically, so you should be keeping yourself updated. And people don't do that, and that's why they, uh, write the older way of code in the new era. So that's one thing. Uh, other than that, uh, the review is done. Uh, the the language syntax is done. If there are new paradigms as part of any framework or library is coming, then you should be following that. Like, uh, people, uh, initially was using Redux, then they go on with Redux Saga. And then I think, currently, people are using Zestran. So you should be, uh, keeping track of what is coming new as part of that particular framework or library, uh, if you compare to React. And then, uh, you you should keep yourself updated with that one too. So that's I think every developer should know.

Okay. So, basically, for the error management in a React Native app, uh, I should be having a global error handler at the app level. So it will be wrapping the whole app around it. And then whenever any global error happens, it it will throw, uh, uh, the required component or fileback component. Uh, I think, uh, suspense is also supported here, uh, in the act. So I think, uh, we can use that one too to basically, do the error error, uh, management. Other than that, while creating previously, people have created error boundary too where we used to catch the error and get to know, like, from which component it is happening. So, uh, we can write a custom function to get idea what particular, uh, thing is, uh, failing or what particular component is failing in the development mode. Uh, for the production mode, it's a bit different because, uh, in the production application, uh, the application is customer facing and customer doesn't want to go in, or you don't want to show any, uh, technical kind of errors into the, uh, production application. So in that context, the error management differs over there where, basically, uh, we change default back compass to something else, uh, instead of, uh, developers, it's customers facing. So customer will, uh, say, uh, see a generic error component maybe where it will say something went wrong or a API gateway down or, uh, yeah, come back or try again, something like that. But in case of, uh, the developer, uh, facing, uh, or the developer's build, basically, where you should be getting, uh, like, what component is, uh, failed and what are the stack you need to follow to, uh, go through that error, basically, or to debug that error. So that's the answer.

It wasn't the system I have designed, but, uh, like, I have done the migration from PHP services to Node. Js services and what, uh, like, why it was hard because the PHP server was monolith, and then, uh, the database band, it, uh, was also connected tightly connected to that particular application. The problem was, uh, like, when we started migrating to Node. Js microservices architecture, we migrated, like, feature based where, uh, many of the services, uh, were interdependent on, uh, the data services or the shared services, uh, for resources. So, uh, like, that was the complex task, uh, I'll say. I have, uh, done previously with the partnerized client. The issue we followed, uh, the the major issue was, uh, like, uh, supporting the existing, uh, existing production, uh, website as it is or the existing product as it is and then updating to the new feature. So here, here, we use the, uh, versioning system. So we created different v one, v two, v three APIs. And then, uh, like, first, we created the APIs once the APIs are well tested, and then we connected that v two, v three APIs by changing the URLs in the front end side. And then, uh, like, by thorough testing, we moved it to staging. We test done the, uh, staging, and then we done UAT as well. And once, uh, we get go ahead from the testers, uh, from the testing team, uh, yeah, we deployed it to production. So that's the way we followed. So I wasn't the one who designed it, but, yeah, I was the part of team, uh, who built it, actually. So that's the, uh, like, migration from PHP services to Node. Js services is the most, uh, complex thing I have done so far in the back end system.

You like the function to calculate the total amount per day table. And if the table is on the table wheel, which is constant for all. And this one tip that is added for each table. How do you use green code principles to improve this function? Additionally, how would you modify this function so it could be used across different tables? I want different restaurants. So if I see the JavaScript code over here, so it's creating a, uh, constant object, like, person, um, one amount, person two amount, three amount, tax percentage. In the raw bill amount, it's creating raw total and then calculating all the three amounts into one and then adding tax amount. Now it will throw error here because, uh, we show it shouldn't be using const if here it is going to assign the value again. So if you want to do it, uh, we can create, uh, like, raw amount or something, some kind of variable, and then raw total will be a different one. Uh, other than that, uh, I think okay. To create this function for different table. Okay. So the problem I can see here, like, if the per number of people, uh, increases, then, uh, the number of parameters will increase. So instead of doing that, I think, uh, we should be providing the table reference over here. And I think, uh, the table amount that, uh, may include the, uh, like, person one, two, three depending upon the person present at the particular table. So instead of the initial three parameters, we can have the table variable, uh, where, uh, it will be object having the amount and uh, other, uh, related details to the people on that table. What about different restaurants? I think, uh, if you go class based over here, then creating, uh, class for, uh, the, uh, restaurant and then class for, uh, each table will make more sense because I was being a part of one of the, uh, one of the project was point of sale application. In my experience, it was still paused where we used to do in such a way where basically table, uh, like, we had this point of sale, uh, software where basically, each table were referred as a object. And then, yeah, for the, uh, different kind of, uh, restaurants, for example, if there is one floor, like, Ground Floor and our First Floor, then we used to, uh, switch tabs in between them. So in that way, I think we will be providing the context of that particular restaurant as well with along with the table. Or within that table, it will get the idea, uh, like, where that table situated is in. So I think by creating the first parameter object in such a way to have the table details and the restaurant details, we'll make more sense instead of having multiple parameters to, uh, uh, get the person amount. Again, the tax percent is a 12%, uh, which is so we can have a constant variable, uh, which, uh, will take care of it. And then by changing that only, it will be, uh, changing in all other positions. And tip is also again, uh, will be part of that table object because there can there is no standard way of tipping, uh, I think. So, yeah, it will be depend on each table, I guess.