Anil Singh

Right. So, uh, I've done masters in computer computer application. I have around, uh, 11 years of experience, uh, in total in Magento. In in total, it's around 14 years. Uh, in Magento, it's 11 years. I've, uh, worked both as an as an individual contributor, uh, independently on projects and as well as, uh, part of the team. I've worked with, uh, clients from all across the globe, from Europe to, uh, US and, uh, perhaps not with Australians. So but, yeah, but to Singapore as well. Uh, I've done certification on Magento. I've just recently did a Adobe Commerce certification as a business practitioner. And, uh, yeah, I did, uh, I entered 1 developer certification as well, uh, in 2015, and now I did a certification with Adobe Commerce, uh, business as a business practitioner. The last company that I worked for was Acuna Global. That's it. That was a US based organization. And, uh, there also, I worked as a senior developer. Before that, I also had the chance to work as a consultant where not only Magento, but I had a chance of inter integrating a lot of things like OC optical character recognition, Microsoft Dynamics as a as a as a back end, and then have had the chance of actually working on a bit on GraphQL as well, uh, in that project with Polo. And I've worked with both startups as well as slightly bigger organization. So so I had all of the chance to work on almost all the aspects of Magento till now. So quite confident of that. Yeah. Thank you.

Engineer is solution to migrate. Engineer is solution to migrate Magento 1 module. Magento with emphasis on data integrity. So from Magento 1 to Magento 2, uh, and with an emphasis on data integrity, though. If we, uh, the whole structure is same. Although there are tools as well, but those tool normally don't work. So if there is a module, uh, which which is there in Magento 1, then, uh, then we would have to if if this if the it it is an ex external third party, uh, marketplace. Its model is there in the marketplace, then we'll have to check whether it's there on Magento 2. If it's written in the existing system or if you had system that is not there, they would have to write it from the scratch, uh, considering the folder structure, which is now compatible with applicable to Magento 2. And, uh, if if this question if I don't know whether we understood this question correctly or not. If it's related to, uh, migration of Magento, uh, database as well, then it's there is there are tools as well, uh, database tools which help migrate midgetto1, data to midgetto2. Uh, but in terms of the mod module, if it's a marketplace module, then it's, uh, it has to be an upgrade upgraded version that we need to, uh, use, uh, have it upgraded. But, uh, if it's, uh, if it's in inbuilt, uh, or in house module, then we'll have to write it from the scratch, uh, considering all the, uh, all the compatibility issues with the Gen 2. Thank you.

Steps would you take to resolve a conflict between 2 Magento extensions, uh, affecting JavaScript functionality. So, normally, whenever there are 2 extensions are, uh, there is a conflict between the JS of 2 extensions that normal call is to change the variables. Let's say, if we have there's a extension that using the same variable, then we'll have to use a no conflict function in JS. Uh, but, uh, then then in that case, you'll have to rename the variable in 1 of the, uh, one of the, uh, uh, one of the modules so that, uh, other one keeps on working and other both of them keeps on working. I think that that should be it. Thank you.

Mechanism to ensure, um, merging to updates automatically. Implement critical. Automatically crit okay. Um, critical security patches. So in that case, we'll have to write, um, say, uh, shell or a command, uh, a tool automatically, a cron, which basically checks for, uh, security patches. If there are security patches, then, uh, it, uh, that commands, uh, through the cron run, uh, is is basically, uh, execute the security patches which are which are there to be implemented. So I would say through the con, uh, using, uh, perhaps a module and a command to execute through the con. Thank you.

Establish a process to update and test Gentoo's front end JavaScript libraries with minimal user impact. Okay? Test. Okay? Uh, front end libraries in JavaScript. This jQuery is there, but, uh, one of the most difficult is knockout JS. Knockout JS handles the checkout process. Checkout process, uh, is difficult to customize sometimes, and it impacts the user. So we'll have to, uh, if, let's say, there is something and can be managed through a jQuery because jQuery easy to manage. JQuery can it's it's far more flexible. So if, uh, that, uh, section of the page, let's say, in checkout also, it can be managed through jQuery, you will we will try to use it through jQuery rather than using Knockout. Knockout has far more complications to and lot of lot more code to implement. So that, uh, that's, uh, what I would suggest. Thank you.

Construct the Magento widget that gets data from GraphQL, uh, endpoint and updates using this JavaScript without a page refresh. It gets data from the JavaScript and GraphQL endpoint. Okay. Updates. I'll have to check this. Uh, I've worked on GraphQL, but only with the sales order. Uh, and that was related to the fetching the sales order, not exactly, uh, uh, fetching the data from the GraphQL and update it in here without the page to fetch. Something which I I I need to check it check this before giving any any concrete answer or more defined answer. Thank you.

To use for form validation. Identify what is wrong with the use of this operator and suggest the more reliable to check the form period value. The form period is available in that. The email field cannot be empty. Okay. So what is wrong with the use of so, basically, it's checking blank email input value. If it's blank, then it makes it a lot. No. So double equal after the meeting. I think if if it's if it's a triple operant, then it's, uh, checks for both both case sensitivity as well. Um, I think that could be one of the issue. Otherwise, I'm not an issue. Thank you.

WPG and Houston, which is to maintain to more testing why it might cause performance issue, how it may not be as bad meeting is visual activity. Okay? Public function case customer order, customer ID. Collection case to order collection. Create an ad field to select. Add field to filter. Customer ID. So it's basically fetching, uh, an order collection factory, and, uh, add field to system. It's basically fetching all this all the values of, uh, of an order based on a customer ID. So for for each collection as order order dot get data is what, uh, each order and this. So one way to optimize could be to remove star and use only certain fields from the order collection factory. So the remove star and, uh, add field to select would have perhaps an array of fields that you want to add to so that, uh, because I in in by default, because an order collection sends around 30 to 40 fields in a single order object, which is huge or even even more. I mean, I may be mistaken. So if it's if you want certain fields, we would have to remove star asterisk, which is there, and replace certain fields. And, uh, so that it will be faster. That's one of the point it may cause, uh, an optimization issue. Rest of it is just just the fetching of, uh, array and displaying it. Thank you.

Architect the Magento system that can revert back to previous stable states. Post upgrade while handling light from action. Again, it's it came to go back to previous stable states, post updates while handling light drum action. Okay. Okay. Okay. Okay. So perhaps, yeah, perhaps, the first would be to, uh, uh, let's say, if if an upgrade fails and we we are required to, uh, there had there are basically 1st would be to take the backup of the whole application, whole website. Then, uh, if let's say there is a there is a problem with composer install or composer require the new function or or the new version, uh, basically fails, then we'll have to, uh, there is always a you can, uh, we can have, uh, come certain commands, SSH commands or shared commands, which perhaps on Ubuntu, the NGINX server may be using, which which if if there is an error, uh, then it automatically, uh, takes, uh, points to the new points to the old application, uh, immediately before we and and then after that, we can actually, uh, have a similar environment, uh, similar to the production and have it, uh, have an upgrade run over there before. So, basically, it will be better that we have a a replicated environment of, uh, replicated with the, uh, production, have, uh, have the same application, have this have it run parallelly, have it run before the, uh, before the upgrade was, uh, to be implemented. And then if it's done, then we can actually point to that environment or point to that, uh, point to that IP and straight away so that there is minimal, uh, downtime while, uh, after an upgrade has been has happened. Thank you.

So how would you enhance existing agenda to ecommerce site, okay, to support a subscription based model. How would you enhance an existing genotype, okay, to support a subscription based model? Oh, subscription based model. I couldn't understand the question. Perhaps, uh, subscriptions are if you're talking about subscriptions are part of Magento, uh, um, but that is part of the newsletter subscription. I we need existing to a subscription based model. Perhaps we can use a newsletter kind of functionality, which is already there, but, uh, we'll have to look for, uh, we'll have I'll have to understand it more clearly than just a single line of subscription based model. Perhaps an example of 1 or 2, uh, websites would have been better. And then, uh, then a deep, uh, r and d would be required to give a exact answer. But in terms of subscription, uh, as a terminology, Magento has a newsletter subscription that we can use to what subscription based model would be something else. Anyways, thank you.

You optimize the loading of Magento page assets to enhance user experience? How we optimize the loading of Magento page asset to enhance user experience in mobile. Okay. So mobile devices, uh, there are 1 or 2 ways to actually do it. Uh, the basic would be to, uh, to set up a different user experience in terms of mobile. 1 is to use a PWA. Uh, PWA or an app that we can use. Uh, app for app, we need, uh, different technology altogether, like, uh, Swift or something. But the PWA can be, uh, can be done, uh, using the default functionality, but just that some sort of React, uh, application would have to be, uh, added. But, uh, in terms of, uh, optimizing, we we can do a lot of things. Especially, we can reduce number of calls. Uh, we can check whether it's for mobile or a or a mobile device or an or for iPad device, then we can reduce the number of JS calls. We could reduce the number of images to be shown on the we can have a different, uh, uh, different UI altogether. Uh, we can put a check, uh, on the, uh, on the index as well because I had I remember we had done something similar to it, uh, where, uh, a check was put to check, uh, to, uh, basically compare whether it's a mobile device and then render a different layout altogether. So there are 2 or 3 ways of actually, uh, doing it. Optimization can be done both on desktop as well as on mobile in a, uh, in a different there are there are various ways of actually achieving that. So whether to, uh, compress the JS and all these things, whether to reduce the mobile, reduce the images which are there on the mobile devices. Same way we can have, uh, different sort of caching mechanism that you can use for optimization. There are lots of things that we can do. Thank you.