Nakka Sivaram Yadav

Yeah. Myself, Shiram. Yeah. Uh, I have started my career with the Visa. There I have worked on, like, a few ecommerce applications, uh, one education application. And then, uh, I have started with the collab notes. Uh, that is also, like, a health care product. There I have worked on, like, health health related records to this station. Then after I got opportunity with Concentrix where I have worked on, uh, in social media kind of application. So this is the, like, a with organization, like, a more tech where I have worked on, like, with the fiscal this automotive, uh, in this application. Then, uh, we post, like, a point of sale. Like, it is also kind of weak. Ecommerce application. We can, uh, load register on onboard, like, commerce, uh, platforms into the flights retail retail ecommerce into the flights. Uh, then there, the crew member will do that point of sales. Like, that is my, uh, career background. Coming to my education background, I completed b tech in electrical engineering at the inter engineering college. So that is my, like, highest level of education. Like, briefly, this is for myself.

Can you outline strategy for casing, uh, uh, caching data from this API case in an iOS version using Code Data. Yeah. By using Code Data Code Data, we can create, like, a DB by initializing the Code Data stack. So it will use manager object context object like a persistent store coordinator and a manager object model. Manager object model act as a, like, a DB schema. So once we prepare our DB DB schema between, like, uh, how the, uh, entities how the columns and how the entities are connected by using the relationships. So after that, we can, uh, we can sorry. After that, we can load whatever that data coming from the rest APIs into the core data. Um, if any if any, uh, further AP calls are required, instead of doing, uh, rest of the AP network AP call, we can check-in the core data. If the data available, we will, uh, we will, uh, we will not do the AP call, and then we'll get back from the core data and we'll display in the in the app. So like that, we can cache it.

Describe the approach to implement lazy loading of emails in your capabilities and so yeah. Lazy lazy loading is the technique. Uh, instead of loading all the emails 100 of emails are at the same time, Whenever the that cell coming into the visible area, that time only we can load the images lazily. And also, we can use, like, a caching mechanism, like, by using NS caching. So if the image is already available, we can load from the cache lazily. If the image is not available, we will, uh, get from the summer server and then we can dump into that to NS cache. So like this, we can load emails slowly based on the visibility of the cell that I'll do itself I mean, that I'll do.

What strategies would you apply to manage the steady effect efficiently in a complex area? What strategies would you apply to manage state efficiently on that? Yeah. We can move at state at state, uh, property wrapper and binding property wrapper. If that variable is, uh, changing inside the scope of that particular view, uh, that is the best way. If that, um, we if the variable find data find is outside our, uh, view scope, then we can reference the inside data, uh, our SIFT UI view by using at state object or at at at at at at at at properties. I mean, property graph. So this way, like, uh, can easily maintain the complex steps.

What is the best practice for managing memory when dealing with large collections of data models in iOS? Uh, best way is to dump to save them into 1st either data either database, and then we can read from the database as the batch by batch. Like, at the time, it is not required to load all the data models into the table view or collection view. So batch by batch, we can load, like, by using page in this and technique like that even from server or from DB also.

What approach would you take safely unwrapping options instead? Yeah. We can unwrap options using, like, a uflet, gauntlet, or anil coalescing operators. Uh, based on the scenarios, we can go we can go for either of 3 options.

Uh, look at this code used to process data using for data, what could potentially go around here, and how might this affect the app performance or stability. Okay? Persistent container view context. Entity and this entry description for entity and user in context. This small object entity. Entity and this setting context. New user set to value John for key name to try catch to find look at this code. The user would assist data. You can put it a lot. Could you see and go down here and then how might you be able to have opponents or stupidity? So here, uh, key I mean, keys, we are manual. Your keys, we are, uh, doing manually I mean, uh, hardcoded. Instead of hardcoding, we can use, like, properties. And also, entity also, we can directly create from the, uh, user user entity. It will use, like, a user context. If we give context, that will give the entity. So based on that, we can add directly, like, when you use a dot name, equal to like that, we can do. This way, we can, uh, potentially, uh, we were we were looking at the keys, uh, we can, uh, easily reduce uh, the thing. Yeah.

Analyze this block of code, can you explain if follows a solid principle with a single responsibility? I have not suggested a way to report it. Create user, delete user, update user, log user in. Log user in, log user, or fetch user. So single responsive filtering particular entity has only one one one actor. Actor in the sense, like, the change coming from, uh, employee I mean, management that related to one actor. One actor are one responsibility. So in that in that in that aspect so create user, delete user, update user, like, uh, fetch user related to one kind of, uh, one kind of act up, like, a responsibility. So we can bring all these 4 methods under user manager. Uh, then user credential manager, we can use, like, user login, user logout as the separate classes. I mean, in the separate class with the class name as user credential manager. So this way, if this will bring this will make, like, uh, user manager is one actor. It has some responsibility. And also, user credential manager is another actor. It has some other responsibility. So this way, we can make that responsibility split into the between the two classes. Makes it will follow SRPs in this way.

Difficult. Very hard. Can you detail how you would use GCD for performing concurrent app licensing as a well managing field safety with core data? Yeah. We can use, like, uh, context to perform and wait. Uh, it will do, like, all the operations. It will add into the one background queue, uh, where it will perform, like, serial manner. And, also, directly, we can use context dot perform. It will do concurrent operations. So these are, like, uh, thread thread shape. So code data by using these 2, we can make, like, code data like a dataset. For that, we can use new background context instead of new context. So it will be more, like, useful and useful and, like, more, uh, concrete approach.

How would you approach unit testing in your product that utilize both the Wiki and Safety APIs? How would you approach in a custom union file that utilize both the Wiki and the etcetera enterprise? We can we can use, like, a c test class based on the whatever interface, and then we'll create, like, a view model. And then that view model, we can isolate and we can test any any interface. It is fine.

What would you characterize when setting up a CSV that can't exist in iOS or private? Like, it it will be we can create 1 now. Suppose we are we have the code in the bit bug bit bucket. If any code commit or any any push happens, like, any PR pull request will happen from source to distance match. That time, we can write 1 webhook. That webhook will trigger, uh, that something is new is there in the web Bitbucket server. Then in the Jenkins server, that will, uh, check out that code from Bitbucket to Jenkins server. In the Jenkins server, we will have the pipeline. It has, like, clean and the checkout, 1 on the one stage. Then we have, like, a a version version info setup. Then we have, like, a, uh, like, a click, like, uh, build build the app, then we will do unit test on top of that. After that, we will create, uh, that IP like bill. Then next stage, we can deploy that IP to particular environment like either either, uh, either, like, get test flight or the more thing is there, like, Optimus, uh, Optum Optimus. So, like, we can start to this, build a better plan.