Jabid Abdul Hamid

Myself and I am from Assam. I have done my BSc on 2021, and then I joined Kudos Finance as a software developer. There I worked on Monstech development. There they had a product to manage loans, and this was a loan to users of small-scale businesses. So I, with my technical team, used to manage the platform, which they used to manage internally within their team, to manage things. I worked on that, I used database services, a full stack, database services like S3, EC2 instance, Redshift, this kind of thing I've used. So after working at that organization, I switched to Google Technology Private Limited in February 2022. When I joined this company, the first project I worked on was token metrics. That was basically on a cryptocurrency-related platform. It used to give you the complete portfolio of NFTs on the exchange, on the cryptocurrency we have, the Ethereum chain, everything you could connect and look at the pricing. It used to have, like, future expected pricing using ML. There I was hired as a monster developer. And in this, I have worked with both front end and back end. For front end, I have worked on React. I have used and designed these components to make reasonable components. And for back end, I've used Node.js. I've created, like, tables for coin, Digi coin updates, and all. I have created work on cron jobs and then also worked on other services like authentication, Stripe subscription, and all. So from that company, I moved to another project called Klarz. Klarz is a retail-based company. It used to catalog the retail products. So my task was, in the back end, I used I had made a pipeline using AWS services like step function, Lambda, S3, SNS, SES, Redshift to match the business requirement. And the business requirement was to get data from Kafka, Apache Kafka, and needs to map according to the business requirement and then move to DynamoDB and S3 bucket. So I made a pipeline using Lambda and all and created the whole thing. On a daily basis, it used to work. So, I then from this project, I moved to I have worked on some other projects like, there I worked as a full-stack senior developer. As a lead developer, I was working on that, like, crypto stream. It is, like, for crypto-related articles. And I've also got a member Postera that used to manage tasks within a team. And then, I have joined Cloud Neto. I've worked on Cloud Neto. That is a cloud management, cloud optimization, cost optimization. Here I made the whole platform and the complete architecture and the building of the back end, everything. I worked on it, and I with my team.

Even the CSS model for it has yet to come. I don't know the issue with the use of "important" and how it might affect feature style, styling, and maintenance. Given this CSS code for a React component, the issue with using "important" and how it might affect future styling is as follows: In this class attribute, this component class, we have a styling attribute, styling keys, such as color and background. In color, we have marked red as the type of color, and it is marked as important. The issue that arises is that wherever we implement this class, this component class, there, this color will work as it won't be overridden by inline CSS. It will continue to reflect red as the color of the text. If we give inline CSS to the component inside the class component, wherever we use content or text color, that will not reflect. The important color will, and the red color will reflect. We will get higher preference. In this way, it will also be static, so we will not give any conditional color on events. So, if we want to change the color, it will not work because it is marked as important. It is working as important.