With over seven years of experience in software development, Jubin Patel is a seasoned Developer adept at crafting innovative solutions across diverse domains including e-commerce, healthcare, media, gaming, and fintech. His expertise spans front-end and back-end development, with a strong proficiency in technologies such as React.js, HTML5, CSS, D3,js, Angular.js, Node.js, Python, SQL, NoSQL and various cloud platforms. Jubin has a proven track record of delivering high-quality applications, having worked as a Senior Software Engineer at EPAM Systems and as a Freelancer with multiple startups. His hands-on experience in translating UI/UX designs into functional components, integrating authentication systems, and conducting rigorous testing and code reviews underscores his commitment to delivering robust and scalable solutions. Jubin's technical acumen, coupled with his passion for innovation, make him a valuable asset in the software development landscape
Contractor
Multiple StartupsSenior Software Engineer
EPAM SystemsSystem Engineer
Tata Consultancy ServicesReactJS
Node.js
AWS (Amazon Web Services)
Design pattern
Microservices
Javascript
SQL
NoSQL
API Design
Responsive Design
UI/UX Design
Figma
HTML/CSS
Python
PostgreSQL
MongoDB
Firestore
Github
Bitbucket
AWS
GCP
Heroku
Firebase
Elasticsearch
Microservices
Redux
D3.js
Express.js
Material UI
Ant Design
Jasmine
Karma
Jest
Jenkins
Mixpanel
Google Analytics
Auth0
Contentful CMS
RDS
Pyspark
Amazon SageMaker
Amazon RDS
React.js
Angular
GCP
Microservices
Redux
Material UI
Redux
Material UI
Hi. My name is Jupin Patel. I have over the over 8 plus years of experience in software development. I have worked with various service based companies like TCS and EPAM and also with multiple startups like Made by Hidden Infinity, Huddl, uh, Quantenna AI, and Project Symant Momentum. Uh, I have, uh, around 8 plus years of experience working in React, Node. Js, Angular, and Python. I have, uh, developed multiple front end and full stack applications. Uh, I started my journey as a, uh, developer with Tata Services in February 2016, where I worked with a client in health care where we developed multiple marketing and internal applications for the client. After that, I have worked with, uh, worked as a freelancer with multiple startups where I developed multiple ecommerce and Fintech applications for the client, uh, uh, in React and Node. Js, uh, with AWS, GCP, or Heroku posting. After that, I worked full time with as a senior software engineer with EPAM Systems, where I worked with 2 major clients, which is London Stock Exchange Group and Thompson and Reuters. Uh, sorry. Uh, where I worked with the full stack applications in Angular or React and Mooges. Uh, currently, I'm working with a startup called Projective Environmental, uh, where I'm developing a AI based product for the client in React, uh, to basically automate, uh, the reports, phase 1 and nominal site assessment reports. They write in word, uh, to a web application using, uh, Draft. Js. Uh, apart from React Node. Js, Angular, and Python, I also have experience working with technologies such as AWS, Google Cloud Platform, uh, Heroku, uh, Auth0 authentication, uh, Cognito authentication, uh, Google Analytics, uh, SEO implementation in the application, uh, based on the uh, feedback given by the SEO executive, uh, then Next JS, Express JS, and multiple other tools and technologies, uh, that were used by multiple clients. That's it regarding my experience.
Yes. So we should try and avoid using important because if we use important, it will override all the styles styles which are returned after it if important is not used. So, basically, say I am implementing a color red important in component class right now. So, basically, if I have any, uh, style series implemented after it, it like, color blue without important. So, basically, that blue color will be overridden with red because we have returned important there. So it's important to or using import important as much as possible until and unless it's very much necessary to do it. And even if we are implementing it, we should make sure, like, we, uh, try to do it at the component level. Uh, the smallest component level, like, say, if I'm overriding, I should override it at, say, a button, not, uh, implement it in a global style because global style will override everything if we are not using important in in, uh, the application. So that has some of the things that you should avoid.