Sahil Seta

Sure. Uh, I'm Satil Sita. I, uh, started my journey, uh, from PHP WordPress and by, uh, developing custom themes and plug ins. And then I later on, uh, started gaining Nextiva, good interest with JavaScript, TypeScript. So I, still started logging it, and I got a good opportunity to work on the, uh, Angular, uh, framework. Then I moved to totally moved to JavaScript. And, uh, during my, uh, period, these 4 years of period, I also got chance to work with, uh, Node. Js, React. Js, MongoDB, and also with, uh, major libraries like, uh, tailwind CSS, Bootstrap, uh, DHTMLX to create the, uh, schedule Gantt charts and the kind of our complex, uh, data models data views. And, also, I have a good experience working with product based I I mean, uh, designing and developing the entire product from scratch as well as, uh, by, uh, defining a set of reusable components where I can where I can, uh, reuse the view. Use the UI. Yeah. So that was it from from my

Yeah. Uh, to manage the interaction between Angular and I mean, the front end and the back end team, I will definitely, uh, help them out with the requirements, firstly, what are all the requirements from my side, what are all the required what data I need, and then I'll help them with the JSON. Like, type of the JSON is what type of JSON I will require. And I will, uh, try to optimize the UI as we we as much as possible to to reduce the API calls and, uh, the number of APIs to be, uh, developed. And also there are some, uh, best practices to follow while, uh, integrating the APIs in front end like, Error handling is the major part while, uh, let's say some second person is developing the API. I should tell them that, If a specific response is not coming from the AP from the front end or specific key, uh, inputs So not coming. They should handle the API, uh, they should handle the, the errors appropriately and the same to be followed in front end

Uh, personally, I will suggest to, uh, use most of the reusable UI modules, the, uh, lazy loading routes to, like, enhance the user experience, the load reduce the load time. Also, the SSR is a good feature to, like, quickly load the 1st screen, and that will give the, uh, users a good sign that your website is having a a overall, uh, very enhanced and, uh, genuine user experience. Also, other than this, uh, we should handle all the, uh, most of the errors properly. We should flow. We should think like a user while developing the front end. That will be the major aspects. This will be the major effects. Other than this, I will definitely try to optimize the UI as much as possible for most of the screens. Like, it will be a tablet or mobile phones and laptops. So that that will be from my side, that will be the best scenario to enhance the overall user experience. Also, we should follow these standard practices while developing the apps, like, uh, following the coding practice best practices for for coding and, uh, removing the unnecessary libraries if there are and not using the, uh, libraries for such, uh, basic tasks. We should always for go for a custom development if the if the application requires critical, uh, application is having criticality with the performance.

Uh, PWAs are a good way to provide a user a feature where they can, uh, if they are able to access the applications via the browser itself and also for their convenience. If they won't don't want to each time they don't want to go to the browser and ask for the website. Then, uh, also, they can, um, I mean, add them via add them on your mobile screens while using the Progressive Web Apps while using the, uh, feature of the Progressive Web Apps. It is similar like, uh, web view where, uh, in the application view, we load the, uh, application and your applications with the help of some, uh, features. We have some predefined predefined set of libraries. And, uh, it is a good feature if we are looking for a ecommerce or a blogging website or something like user centric application. So that will be a good way to, uh, expand the user criteria and usability, uh

So in, uh, as per my, uh, answer, the continuous integration process will help us the, uh, the overall improvement of the code quality. Because, uh, while we are building, we can't think, uh, the entire scenario and the user, the, uh, each case where the user will be doing what what are all the user accents on the applications. So while, uh, whenever whenever our dev application has completed, like, it is developed and as going for testing, after the testing, user will be using the application. During that session, we can, uh, follow-up with them and get us feedbacks get feedbacks, like, what are what are the issues they are facing? What are the problems they are facing? By this way, by this feedbacks, we can rapidly improve the applications, that will be a good way also for the code quality to, uh, to in for the developers to improve the code quality as well. Because we are continually, uh, continuously, uh, growing and expanding the application, and it's code base as well. Like, uh, there will be some real parameters as well, which we can't check during the development phase. So that could be cast in this continue continuous integration process.

Yeah. Uh, here they have used the component design pattern. I mean, the component There is a, uh, app component. There is a class named as an app component. And, uh, in this, uh, there has been decorator component decorator which has its own property, selector, template, styles URL. So here we are not, uh, defining the template URL. We instead we are directly putting the HTML. Uh, not even the HTML, but a string where, uh, we are pasting we are printing a string in the template in the template column, and, uh, that That too includes our variable name which, uh, has a value, which is a type of string and, uh, has a value as Angular. So it will print welcome, Angular, and it follows the component based model. Uh, however, there are some certain other, uh, patterns which we can, uh, use to develop the Angular applications while which is a, uh, module based components where we can provide we can use the lazy loading as well if the application is larger in size. But for a smaller number of applications, like, for a smaller amount which is having a 5 to 7 pages or, which is not going to handle the large number of data. It is fine to use the component based,

Sure. Uh, here we have a class named App component, which is, uh, which includes variable type of string and, uh, n g on it. Firstly, we'll, uh, come to the n g on it. And generally, it is a, uh, angular life cycle hook which is being used to, uh, initialize the, uh, application, uh, the sorry. The component with, uh, some of the some of its, uh, values. Let's suppose, If you want to call the API or we want to initialize something or we want to assign some default values to the variables, which we are doing here, We are, uh, assigning a value to message by accessing it like this dot message is equals to Hello. We are putting a value as hello, and, uh, we are printing it in our template Angular, uh, Angular component template. So this is the major role of the NGON edit method. And, uh, NGON edit method is something which will be called While, uh, the component will be, uh, injected in the UI, injected in the screen, uh, and Just before the, uh, just after the constructor, it will be called. And after the engine changes.

Yes. Uh, in my past years of experience, uh, I've, uh, faced a numbers of numbers of epic Yeah. Uh, numbers of problems which were from the UI Effective as well as from the back end perspective. But, uh, in this question, you asked us in Angular as compared to ReactOS. So if we talk about the, uh, the global data management As we as we are aware that rejects JS provides a good, uh, library which is Redux, which is a store based state management, uh, library using the access application mostly in almost almost big, Medium to big scale, the access applications will have the, uh, this, uh, library. But if I talk about the, uh, angular, I most I I prefer the subjects and behavior subjects, which are the, uh, features of RxCS library. Uh, also, there are In new year angular versions, we have these signals, which is a great way to pass and store the data with multiple, uh, components and, uh, the services. So that this is what I will, Uh, definitely, uh, use. And also Angular in terms of the change detection, I faced lot of issues while, uh, implementing the DHTMLX diagram, but I faced I, uh, solve it with the detect changes. And other than this, I, uh, developed some real time applications where, uh, the Microsoft Excel, like, feature is developed in the table. User will be able to,

Yes, Shirley. This is the, uh, one of the major features if we talk about the, uh, SPAs and front end development. We should always ensure the code reusability everywhere during the entire application development. And if we talk about the RejS, RejS is something component based library, and Angular is a different thing. It it is an full fledged framework. And, uh, generally, framework defines the way, uh, it has a very defined way of working and developing the occasions. Generally, in my current organization, we have I'm working as a I'm working in a product based company where we have a module shared module where we define the set of reusable components. Like, uh, I have a table, uh, static table where I can part. Uh, I can push the columns. I can push the data. I can push the callbacks, which I want to, fire when some particular column is being updated. And, also, there are some there are few other components as well, like card, uh, convo view. We have a convo view with where the user can see the data. So that the usability should be ensured by using in in Angular, by using the input and event emitters, so we can pass some values. And based on the value, we show we generate the UI. In the access. Uh, it has been used with prompts which are a great way to pass the data to the, uh, child component or a reusable component. And also, these stand alone features will uh