Lucky Kumari

Good evening. My name is Lucky Kumari. I am having 2 years 9 months of work experience, which is near to 3 years as a front end developer. I have a good knowledge and experience of creating user friendly applications And it makes technology. My current role is as a software engineer. Here, I have worked for 2 Projects. The latest to be Citrix Cloud success center. My key skills are that of Angular, HTML, CSS, JavaScript, Bootstrap and others related to front end development. I'm also well versed with the responsive design, cross browser compatibility and performance optimization of the application to provide a better user experience across device and platforms. I'm looking forward to get better opportunity uh

Uh, to code review and for unit testing, uh, I would Uh, use a git. And also sometimes I have used Get, uh, on that I have uploaded, like, uh, some of the codes. And also and also Sourcetree for, like, creating the PRs. And after that, like, After creating the, uh, like, PR, uh, they were, uh, senior developers to review the code. So Sourcetree and Git were the, like, 2 uh

To ensure that my angular, uh, like, single page application has consistent UI across all browsers. How do you ensure that your angular single page application has a consistent UI across all browsers? To ensure Consistency in UI across different browsers in Angular single page application. I have used, uh, like, vendor prefixes, Uh, then browser testing. Uh, in browser testing regularly, I have tested my app, uh, in various browsers to catch and fix any inconsistency or bugs. Uh, then I have also normalized or, like, reset the CSS, uh, which can help Uh, normalize default style across the browser reducing the inconsistency. Then in the polyfills, Uh, in polyfills, uh, to provide missing functionalities in older browser that don't Support modern JavaScript features used in Angular app and also, uh, in Angular browser support.

How do you handle asynchronous operations in Angular and React JS frameworks? In Angular and React handling, Uh, asynchronous. In Angular and React handling, asynchronous operation is, like, crucial for managing data fetching, If the calls and other tasks that don't happen instantly. So in Angular, We primarily use, uh, RxJS observables and the HTTP client module to manage asynchronous operation. Uh, observables. Angular relies heavily on observables from RxJS service often return observable to handle asynchronous data stream. HTTP client, Angular's HTTP client module provides methods like get, put, post, and delete to make HTTP request. Uh, these methods return observable that can be subscribed to in, uh, like, components. And also I've used async and await. Using async and await can also simplify handling promises within Angular services or components making asynchronous code more readable. For React, uh, I have used features like, uh, promises, a sync of it, libraries like, Axios or like built in fetch API for handling asynchronous task promises Is a sync of it exhaust to fetch

How do you ensure code reusability when working with Angular and React JS framework? Ensuring the code reusability is crucial in both Angular and React to optimize development. Here's how we can achieve, uh, it in Each framework in Angular components and service, uh, like, breakdown your we need to break down our applications into The usable components and services components encapsulate UI and functionality while services handle business logic and data operations. Uh, then we use module structure. We organize our Angular modules effectively, grouping related, uh, component services and other resources Encapsulate functionalities in feature module that can be easily plugged into different parts of the app. Shared modules, uh, created shared modules containing, uh, commonly used components, statics, and pipes. Uh, these can be imported into multiple, uh, modules across the application from a promoting reusability, Dependency injections, uh, like, leverage, uh, Angular's dependency injection to share instance of service across different components ensuring a single instance and promoting code consistency. In React also, we have used component composition, Hooks and context, high order components, and render props. Uh, basically, utilizing the render props Pattern to pass functions as props enabling the use of logic between components.

As soon as, uh, the code runs, Uh, we can see, uh, like, hello printed on the screen. Uh, n g on in it is the 1st life cycle hook which is being hit when an angular application is, uh, run append on the server Because it is the entry point of any component. So n g on and it basically initializes which whichever that Whichever code we need to show on the screen as soon as it gets loaded, uh, we write those, lines of code in the NG on in it. So NG on in it method is the first method which is going to be loaded as soon as our uh

Design pattern in Angular. Here, uh, com decorator pattern is used. And, also, we can say, like, component based architecture is used in this particular code snippet. So component based, like, this a decorator pattern And, uh, component based architecture

Describe a circumstance where the transition from Angular to React to JS or vice versa led to pricing result and specify the lesson learned. Like, um, in our company, once A large angular application, uh, was there, but we wanted to migrate it to React due to the growing React ecosystem. So a perception of better performance and a more flexible component model. So, however, after the migration, uh, we experienced a surprising increase in development time for certain feature, mainly due to the steeper learning curve of React for their angular experience for our angular experience team. The lesson learned here is that the decision to switch between framework should consider various aspects beyond just perceived performance or popularity. Team expertise, familiarity, and the specific needs of the project should heavily influence such transitions. It's crucial to weight the potential benefits against the cost and challenges of migrating to a new technology stack. Proper training time allocation for the learning curve and a phased approach to migration could significantly, uh, mitigated unexpected