A full stack developer loves to build logic and manage the team for the better productivity. Having transitioned from intern to Full-stack Developer, my journey has been marked by a steadfast commitment to technological excellence and the seamless integration of front-end and back-end systems.
Our accomplishments include deploying scalable applications that support the organization's strategic goals. As I continue to evolve in my role, my focus remains on delivering robust solutions that address complex challenges, underpinned by a collaborative spirit and an unwavering dedication to innovation.
Lead Software Engineer
Compound LLC FZSoftware Engineer
Skugal TechSoftware Engineer
Kudos Finance and InvestmentNode.js
React
AWS (Amazon Web Services)
Bootstrap
tailwind css
Redux Toolkit
AWS Lambda
React.js
AWS services
Lambda
Kafka
Postgres
DynamoDB
S3
Stripe
Paypal
Typescript
Mixpanel
Redis
API gateway
Appsync
EC2
MongoDB
Git
Jira
Firebase
Firestore
Cloud Functions
Stripe
Docker
ReactJS
NodeJS
NextJS
Material-UI
SNS
SQS
Cloud watch
AWS Textract
Redis
API Gateway
Kafka
Yeah. Myself, and I'm from Assam. I have done my b, um, on 2021, and, uh, then I have joined, um, Kudos Finance as a software developer. There I worked on Monstech development. There there had a product to manage loan and this was, uh, loan to the users, uh, to small scale b scale businesses. So I, with my, uh, team, technical team used to manage the platform, which they used to manage internally within their team, um, to manage things. I on on that, I used database services, a month stack, uh, database services like s 3, EC 2 instance, the Redshift, this kind of thing I've used. So after working the on that organization, I switched to Google Technology Private Limited on, um, February 2022. Yeah. When I when I joined this company, uh, 1st the first project I have worked on, that was on token metrics. That was basically on, um, cryptocurrency related platform. It used to give you the complete portfolio of NFTs on the exchange you on the cryptocurrency we have, um, Ethereum chain, everything you could connect and look at the pricing. It used to have, um, like, future expected pricing using ML. There here also, I was, uh, I joined as monster developer. And in this, I have, uh, worked with I have worked on both uh, stack, like, in front end and as well as in back end. For front front end, I have worked on React. I have used and design. These are the thing, uh, to make reasonable components good components. And for back end, I've used, uh, Node. Js. I've created, like, uh, tables for coin, um, like, um, Digi coin updates and all. I have created a work on, um, cronjobs cronjobs and then also worked on, um, like, other services like authentication, auth authentication, uh, like Stripe subscription and all. So from this company, I joined, um, moved to another project called. Not from that, uh, project only, I moved to another project called Klarz. Klarz is a retail based company. Uh, like, it used to, uh, catalog it used to show the retail products. So I my task was, uh, in the back end, I used I had made a pipeline using AWS services like step function, um, Lambda, s 3, uh, SNS, SES, Redshift to, um, like, to match the business requirement. And the business requirement was to, uh, it used to get, um, datas from Kafka, Apache Kafka, and needs to map using the, um, according to business requirement and then move to DynamoDB and s three bucket. So I I made a a pipeline using Lambda and all and created the whole thing. Uh, on a daily basis, on a shitty basis, it used to work. So, uh, I and then from this project, I moved to, uh, I have worked on some other projects like, um, there I worked as for, uh, full stack means senior developer. As a lead developer, I was, uh, I worked on that, uh, like, um, crypto stream. It is, um, like, for crypto related, um, articles. And, also, I've got a member, uh, Postera that used to manage, uh, tasks within a team. And then, also, I have joined Cloud Neto. Uh, I've worked on Cloud Neto. That is a cloud management, uh, cloud optimization, cost optimization. Here, I may, uh, made the whole platform and the complete architecture and the building of the back back end, everything. I worked on them, and, uh, I I with my team. Yes.
Even the CSS model for it yet come. I don't know the issue with the use seem important and how it might affect features style styling and maintenance. Given this CSS code for a React component, please I tell you the issue with using important and how it might affect future styling. So I can see in this, like, class attribute, like, uh, this component class, we have, like, a styling attributes, uh, styling keys, like color, background. And in color, uh, we have marked as red. That is a type of color, and it marked as important. So the issue we make arise wherever we implement this class, this component class, there, this color will be, uh, will work as, um, like, it won't override with the inline CSS. It will keep on continue, um, reflecting red as color to the text. If we give the inline CSS to, uh, the component inside the class class component, wherever we, um, like, use content, uh, wherever we use, uh, text color, there that will not reflect. This important color will, um, this red color will reflect. We'll we'll we'll get the higher, um, like, like, higher preference. So in this way, it will, like, um, it will also, uh, though it becomes static, so we will not give any, uh, conditional color, like, uh, on events. So we if you want to change the color, it will not work as it is important. It is working as important. So, yeah, these are the things we, uh, these are the issues we may get, uh, with this important syntax.