Himesh Aadeshara

Hi, I'm David, and I'm working as a software engineer. I started my journey as a junior developer with Inside Solutions, and I'm currently working with the company. I have 8.5 years of experience in this company. I have worked as a front-end developer and also held a UI developer role. As per my current role, I'm responsible for monitoring four junior developers working with PA teams, and I also work on requirements during the QA process. As far as the technology stack is concerned, I have worked with HTML, JavaScript, jQuery, CSS, and Excelsior JX for three to four months, then AngularJS. Literally, as per the latest trend, I'm working with Angular and TypeScript. Additionally, my latest project involves building on the Electron JS framework, which is built on Node JS. In this project, we communicate with both desktop and cloud applications. We communicate with those systems using a batch process, and we store data in a local database file on the local machine. So, yes, in that project, we use Angular as the front-end part. We handle the back-end modules, and the application is for a desktop application.

We have an back end. So, yeah, in that, like, we are having a back end application communicate by using environment? Yes. Yes. So in that, we are giving both URLs and those things with staging case, like, if we have a staging environment, production, development, local development, and environment. So all these are, like, we can make it communicate with that configuration file with the back end team? Like, back end team also has some specific server running ports and URLs? So yeah. We can do it that way.

What process would you follow to perform code reviews and unit testing in Angular dialogue? Yeah, so we have done that is a unique test case of build dot Kava JS Karma. So in Angular, we are doing that Karma is the unit test compiler. Here are the test cases. And for the process of code reviews, there are extensions like ESLint and TSLint which actually notifies us of errors while compiling time. So in that way, we are performing syntax-level code reviews. And then after, we can manually perform code reviews as well before merging the PR, which can be done by any lead or reviewer in any role.

So, here, the issues we cannot say. We can have an opportunity to perform performance optimization for the core. Call quality can be measured here. So, if you want to, if you can, if health conditions are managed, we should do it that way. Also, most of the issues are when you're trying to get the probability of any object, but the object is null, then that can be the possibility where the JavaScript files throw an error and stop executing. Those kinds of errors are where there are many conditions where, when we fetch data from this server, we are not handling any error part, only the success part. So, most of the things we have encountered are a few reviews. Also, a functional review can be there. If the flow sounds with the functionality, he or she can get the idea about the flow that there might be a possibility that it throws an error. It will not work.

So for performance optimization, we should reduce CSS parts as little as possible for the HTML dome. It will help to optimize and we should not make the dome very heavy. Like, Angular is providing features where we put NGP conditions where we are not needed anything. So, I mean, we need not show unnecessary information. It will remove the dome. So that is helpful, the Angular optimization. Also, there is a thing, like, there are two optimizations while building the app. The Angular app has two facilities where we have two options: one is where we bundle the whole process at the build time and just deploy those things, and render the page. And, also, there is a traditional way where we compile at the browser level, and then it gets rendered. So it takes time at that moment. So Angular has provided a bundle from study while creating the build time. It enhances the thing. Also, there is a thing, like, when we don't need any components, so we should load them in a lazy loading manner. So lazy loading is also there, which is a feature where we only load what's needed. Also, tree shaking is a concept, which is what you'll be

For code usability, there are plugins for Kafka that I don't know the exact name, where we can mention a backend team's APIs and for that, we can reuse the APIs. Also, there's a component where so most probably, here the main case is like, we don't need to do this specific code, ID-based code or parameters, we can make it parameterized, like we can give the parameters and do it work as a standard code practice, the function works with one function, the only task, single function is suppose I have to add something, so that function should work as an addition only. It should not do any other things. So stick with the standard concept. And that way, we are achieving core usability with Angular or React, any framework. It's not about Angular and React, you can have any framework.

Can you explain how it, specifically, the Angular core works, especially the role of the engine method in the component life cycle? So, like, here, the component is an added component, which is a separator, with the selector name like 'approved'. So, the main thing is, your app starts with this component, which is at the app root element, wherever in the application it has been put. So, here, in that, there is a template that is blank. It is the root, so it says that it is the root component. Then there is a style URL handling with the app component's CSS file. So, this component has a specific file, which is known as 'app.component.css'. This component is basically working as a root. Also, the class, here, is Export class AppComponent. The problem would be here, is that there is an 'ngOnInit' event, but the class is not implementing that 'onInit' method. So, you have to first import the 'OnInit' from '@angular/core', then you can use it. As it will give an error, saying it does not have the method. So, as a component's life cycle, the components first function is the constructor, but your constructor is not present. So, then after the life cycle is, the 'ngOnInit' method, whenever your component gets loaded and ready to work with. The first life cycle method will be called, like 'ngOnChanges', and 'ngOnChanges' I guess is that change detected or something like that. Then after 'ngOnDestroy' is there, which is having the first method, which is called after the component gets started. So, then after other life cycles are there, like 'ngAfterViewChecked', 'ngAfterContentChecked', 'ngAfterViewInit', and 'ngOnDestroy'. So, there are 7 or 8 life cycle methods aside. And also, the main role of the 'ngOnInit' method is. Whenever we have to put any components initially, like if we have to get some data on load, like loading that component or just viewing the screen of that component. So, we can put those calls or values there. So, as like the 'documentReady' function for the whole page, it is the same kind of thing for the component level. It is the same kind of manner for the Component.

This is the corrected transcript text: This code snippet has a problem that can lead to memory leaks. The memory leaks are when we subscribe to it, we are not unsubscribing it as a destroy component. There is also a thing. Memory leak is there when we have bound the component, like a group form, to the group. Each element is having a curve form, bound to the input or elements. The main thing is, why we need to subscribe it to the value changes. We should put that on the submit, we can check the form. So that way, there can be a solution where we have to just check all values, and validate those ones on submit.

Our transition from Angular As of now, I don't have experience transitioning from Angular to React JS, or vice versa, but I do have experience transitioning from AngularJS to Angular. That was a drastic change where the whole pattern changed, from a controller-based form to a component-based coding approach. So that was a huge change, and the lesson I learned from it is that when we work with such kinds of things, we should make web tech components like that. There are web tech web components which can be loaded irrespective of the Angular framework. So we can do it that way. That's a thing I've heard about it. Although I haven't worked on that, but yeah, that can be a lesson where, and that could be some common things in that way, we can make.

So these are the speed technologies, like load speed in large scale, that there is a concept in Angular apps, where there can be two concepts, direct concepts like single page application, where we have to get only data from the server and just render that data on the HTML, the HTML part or CSS part are loaded on the browser, and that is also a concept where server-side rendering is there, which is had to optimizing Angular applications. Where the actual HTML passing has been done through, like, on the server and just the HTML comes across to the browser from the server side, and we just have to load it on the browser. So there can be a time of reducing that, reducing compilation and that kind of mechanism on the browser, and we can skip that as it is done on the server side. Like the page comes from the server side. So that is the biggest thing we can do to page load speed. And also, there is an advantage of that. We can achieve a good amount of good SEO optimization, like we can achieve SEO optimization as we expect beyond that. So that is the advantage.