Abhinav Satpute

Yes. My name is Abhinav Sathute, and I have done my bachelor's in computer science, then master's in computer science. I got elected as an intern at Armand Connected Services. So after 10 months of internship, I continued in the same company as an employee. So I have total around 5.11 years of experience. In around 6 years of experience, I have worked on Angular. And I have about 4.5 years of experience in Angular. And a few years, I have worked on Java as well. That's my technology stack.

Yeah, so for the code review process, we are following SonarQube. First, we install the SonarQube link in the ID, then we perform the code reviews also not in a queue, but on the server. And then, before committing, we have a manual code review session, and that's it. For unit testing, we are using the Jasmine and Karma framework, in which we are testing the services, including API responses and how they are handled in the code and component testing. Component testing will be similar to this. And, yeah, thank you.

So, for consistency, I'll use the same libraries for the project. Like, I'll use Bootstrap, I will do the configuration in the app.model.ts. There, I will so there will be a header and a sidebar that will be common for every page, and only internal things will be different, like I will create a few components like buttons and which will be like cards, which will be reusable in every component and every HTML template. So I'll use the same things in every HTML template with different colors and all. So that I'll maintain a consistent UI across all the browsers.

I'm happy to help with the transcript. However, I need the actual text to correct. Please provide the interview transcript.

So for the backend integration, we will use the HTTP client with the REST APIs. And, using observable, we will manage that. We can manage that very well using pipes and all. So, it will be faster to transform data and to get it. And, also, if there is a WebSocket, then we will also use that. With that, we will be able to get the stream of data. And, yes. We will provide the exact JSON format which we need to the backend too. And, if there is a slight change in the JSON format, then we can

Yeah. If the state is changed and then also the UI is not getting updated. First, I'll check the console and the network tab from the browser using browser development tools. There I will check if there is any issue. So, if there is no issue, then I'll look into the code. If the state is changing, then why it's not updating in the UI.

Yeah. And here I can see the observable is subscribed, but it is not unsubscribed. Okay? So, we need to scribe the observable printing cubes of the observable when it is completed. So I'll suggest to unsubscribe from the subsurface available value changes on the observable.

Okay, so here in the template, we are printing the message using string interpolation. And, like, we have provided the style URL as a style sheet app component of CSS. And in the component, we have defined a string and assigned it. So assigned in it will get triggered, and that is a big component, we get initiated. So, on load of that, on the initialization of that component, engine will get executed. So this start message equals hello. So we are using string interpolation for the message to show in the UI. So, this is this will be like open paid data winding from component to view. So this will be a bit reflected in the template.

So in Angular, we have the complete architecture. Okay. So in React, we are dependent on other libraries to use with React. Instead of that in Angular, I have used the RxJS and NgRx. Okay. And, I also, basically, NgRx is dependent on the implementation of Redux. In Angular, we have observables and promises as well as component models. That structure is already defined in Angular. That's why Angular is. We had a problem with large datasets and managing states. So we have included NgRx in the project. So that way, we have solved the complex problem of our Angular application.

So, the code reusability is when we create reusable components. We have to maintain a consistent color, shape, and styling part of any component. For example, any widgets like cards or buttons, or links, such as sidebar and navigation. We already create those things and will use them whenever we need that button and widgets or cards. By that, we'll also use those components in every page, so we can use them for services also. There are four API requests required on different pages and different components, then we'll use the same service. Okay. So that way we can reuse the code for the service as well as the component. That's the benefit of using Angular and block JS frameworks.