Each day, everyone at Springworks comes into work with a true passion for building products and tools for the HR ecosystem. We are artists, innovators, achievers, and dreamers, with a one-track mind to fine-tune the products that we build. Through this series of posts, we showcase our team members, their roles, and what a typical day looks like for them. You can check all the posts here.
Aravindhan joined Springworks in Feb 2019. Prior to joining Springworks, he was working as a UI Developer at Zerodha in Bangalore.
Here at Springworks, Aravind works on multiple projects creating and improving the interactive visual architecture for websites using technologies like HTML, CSS, and React.js.
This requires a deep understanding of the browsers, operating systems, and devices through which users access their interfaces.
What draws a site visitor to a webpage? UI developers know.
Let’s take a peek into the life of a UI Developer at SpringWorks.
What do you do as a UI Developer?
My day starts with a team meeting. We discuss our progress with certain aspects of website improvement and what we need to do to finish our tasks for the day or week.
After our discussion, I spend an hour or two inspecting our code and testing it before going live, if our coding and asset creation is finished that day.
What are the challenges that you face as a UI Developer?
Today, more than half of users access web pages on a smaller mobile device. The Basic challenge is to test the responsiveness of the websites over different browsers, operating systems, and devices.
To solve this challenge, I use a mobile-first approach.
A “mobile-first” approach involves designing a desktop site starting with the mobile version, which is then adapted to larger screens(contrary to the traditional approach of starting with a desktop site and then adapting it to smaller screens).
Generally speaking, a mobile-first approach means building your website with your mobile users in mind, with the primary goal of improving these mobile users’ experience on your site.
What do you like the most about UI design?
You may hear this often, but my favorite part of UI design is when a system I have worked on is finally in the hands of users. I like to see how users interact with the websites and applications and know that my hard work has made life easier for them somehow.
A UI Developer is the bridge between the presentation layer and the backend layer. The developments made at the back-end are presented to the users with the help of a UI Developer.
How do you deal with negative user feedback?
All UI designers will experience negative feedback, but the important thing is what you do with that feedback. I just make sure not to take it personally and make changes that are more in line with the user’s wishes.
Walk us through a day in the life of Aravind
- Get up at 6.30 am
- Go for Football practice from 7 am to 9 am.
- Get home and have breakfast.
- Check my Slack and work emails.
- Check my to-dos
- Attend team standup at 12 pm
- Talk to the team about the on-going projects.
- Write code.
- Have dinner at 8.30 PM
- Chill for a while and sleep.
What do you think about the Springworks team?
I am majorly responsible for contributing individually, so I do not get to communicate with many people for my work, but I do work with the designers directly.
The designers bring me on board to help with the development aspect of the work. Hence we are a part of the team working to deliver a great end result to the end client.
The designers help to fill the gap between the design and development workflows.
Apart from this, Springworks has created a great remote framework consisting of flexible timings, rewards and recognition, and autonomy, which I love.
What advice would you give to other UI Developers?
Don’t repeat yourself [DRY]: a known development mantra that aims to help us not have the same piece of code copy-pasted in a lot of different places when working on a particular codebase.
Simply put, do not repeat your code. Normally, in production code, it’s a good place to apply this.
The next advice is to write minimal code. Use simple, descriptive names for functions and variables – don’t copy the names you’re using in your existing code.