I'm Gowthamkumar, a seasoned Senior Ul Developer with over 12 years of hands-on experience in the dynamic world of software development. From my humble beginnings as a Front-End Developer, I've evolved and grown into my current role as a Senior UI Developer L2, embracing the ever-evolving.
Senior UI Developer L2
Mcfadyen Consulting SoftwareSenior Software Developer
Kanini Software SolutionSenior Software Developer
Kanini Software SolutionsAssociate
Cognizant Technology SolutionsAssociate-Projects
Cognizant Technology SolutionsSoftware Engineer
MatrixCare
jQuery

CSS3 & CSS5

Javascript

HTML5

Ajax

Angular
REST API

Python
Jira
NPM

D3.js

Spotlight

CSS3

LESS

AngularJs

React

Typescript

Bootstrap

Material UI

Next.js

trpc

Highcharts

Oracle

NLP

Image Processing

Jest

Jasmine

Karma

Java

Struts

Spring

Hibernate

SQL

JSP

TypeScript
ICT (Integrated Capability Tool)
Dobilin
Argus
MatrixCare Senior Living
Visualyx
SPOTLIGHT
IDASHBOARD
Gautam Kumar. I worked with a senior as a front-end developer for the past 12 years. I started my career as a front-end developer. Now I'm a senior software and front-end developer. I worked as a full-stack developer as well. My primary technologies include HTML5, CSS3, JavaScript, Angular Material Design, Python, and Flask. I have secondary skills as a machine learning analyst, including Python and machine learning algorithms. I completed a degree in information technology. I worked in three different companies. I have more than 12 years of experience as a front-end developer. Previously, I managed a team with 3 to 4 members. I worked in an environment where all things are automated, from development to deployment. I worked in Agile frameworks, including Scrum and Kanban. I used Jira boards to track everything. For the deployment process, we used Jenkins. For the code repository, we used GitHub. That's all about me.
For the high performance and responsiveness of an Angular application, we used to have an approach like a modular approach, then lazy loading concept, where we have to load the Angular modules whenever they are needed. We use different kinds of techniques, like performance-oriented techniques, to make it a separate library. Recently, modern frameworks are adopting micro front-end architecture and microservice architecture. By using that, we are able to segregate our low-level components. We can make everything from the project loosely coupled. Each and every functionality can be loosely coupled; they can be created in different technologies, and we can merge them using micro front-end architecture and microservice architecture. By that way, we can increase the performance of the Angular application. And we can improve routine productivity as well, because no one is dependent on anything. So each and every one will be able to deliver a particular task.
We can ensure the JavaScript and TypeScript quality features by leveraging TypeScript, which is statically typed, so it ensures we're passing the correct parameters with correct values. Instead of a number, if you're passing in a string, JavaScript might be accepted, but TypeScript will not accept it. By assessing those kinds of things, we can manage JavaScript code as statically typed. Then we can create an interface for that, or we can create other things to ensure our TypeScript is statically typed and we're passing the same parameters. By using an interface, we can reduce the code bundle of that particular application, and we can make use of that because the interface will not compile if it's not implemented correctly.
Yeah, how can Bootstrap be placed in some companies? Yeah. Boot can bootstrap can be utilized in an Angular application by downloading the Bootstrap file using NPM and adding the scripts in the package or JSON file. Then, we have to include the Bootstrap module in the module. Then, how we write code for the Bootstrap, like, By using the syntax we use in Bootstrap, that will be helpful to create a Bootstrap application or a Bootstrap HTML code in that Angular application. By using that, we can achieve the Bootstrap kind of framework. Like, Bootstrap will have other features, such as predefined features, rows, columns, and everything on the grid sector. It will take care of Bootstrap, then we can go for a Toast. We can go for a modal dialogue box. We can go for an autocomplete, search box, etcetera. Those features are available in Bootstrap. We can make use of that. That will be very helpful in designing a very scalable and maintainable solution. Because, by doing everything from scratch is a painstaking process, and it will take more time, and it will increase the production cost as well. By using Bootstrap and other frameworks like Angular material design, we can reduce the time, and we can reduce the production cost as well. Yeah.
This is a function, which is written as TypeScript, adding two numbers. A is defined as a number, and b is defined as a number. And the function will return a value, which is a number. But in the result, we are passing '5' and '10' as a character, or a string. So it will throw an error at that time, during compile time itself. Like, in that code itself, it will not process.
What are the strategies we'd use to manage integration? We used to follow a branch structure from the grid. We have a development branch. We have a production branch. We also have a no remote branch. Once we create a branch from the development branch, we'll be doing our particular functionalities in that branch, and we'll make use of it. Once the functionality has been developed, we'll be pushing the code to the pickup. Then, it will be reviewed by two peers. Then, once the review is accepted and it is approved, it will be merging the local branch to the remote branch, and the development branch. Then the development branch will trigger the CD process. It will continuously try to integrate the development branch into the main branch. By doing so, it will then deploy it using Jenkins. It will check for unit test cases, then it will check for linting errors, then it will check for the deployment process, then it will compile that, and it will deploy the application in that particular environment.
There is an error in the template. No. Actually, if it is a back tick in the template, then it is not an error. If it is an it is I think it is a back tick, so it is not another. We can define a template in the component decorator itself. Instead of using a separate HTML, we can give the template URL, then we have to use this part of the template. Otherwise, it is not an error.
As to be frank, I didn't work much with the scripts, but I have some knowledge about the descriptor. I think there are no issues with this.
To answer this, I never did this, like, handle both the NGINX and Bootstrap layout. I didn't make any layouts that combined these two things, but if you want to handle that, we have to create a sub-layout where we separate them. Because we're creating a Bootstrap layout, then if we're using the NGINX layout, there might be issues with classes between class names, which could affect the UA responsiveness and UA structures in the HTML view. But if there are no classes between class names, it will not create any difficulties.
We can use RxJS from RxJS. We can use all those operators, sake of operator pipe, and make use of that in the API. We can use map, switchMap. Then we can use observables, subject behavior, subject. Those things we can by using the RxJS. We can make it an Angular application into a more reactive, kind of reactive programming application. By doing so, we can manage all the APIs. Like, for example, in the search, we have to go and search for every keyword. We have to give a different suggestion. For example, in Google's search engine, if you type one letter, then one suggestion will come. Then if you type two, three letters combined, then another different suggestion will come. For that, RxJS's switchMap is very helpful. By doing so, we can achieve that Angular application by with more reactive, kind of approach.