I am working as a front-end developer. When I joined Hub, there was a lot to get involved in, such as developing the micro-frontend architecture, a component library and
even defining the workflow of how we get a prototype and transform it into a real application.
Some of the areas I have been exposed to so far are:
How to build architecture in a scalable way
DevOps, working with the cloud and how to build a pipeline
How to create a common component library
How to manage a team and project
How to deliver a product for clients
How to become a better interviewer
A usual day for me in the office looks like this:
[09:00] Arrive at the office which is based in Liverpool Street. I usually grab a coffee with anyone who is in.
[09:30] Join the daily stand-up call where the team discusses what we have worked on so far, and we solve any problems that the team may be facing.
[10:00] Join the daily stand-up call with the wider team to give an update on what our team is working on. Having separate stand-up calls allow us to prevent having too many meetings.
[10:30] Attend the white boarding session - this session is for devs to brainstorm solutions to any complex problems that they may be facing. This usually happens in person so we can make the most of using an actual whiteboard!
[12:00] Go to lunch with any coworkers who are also free. There’s lots of nice places to eat around the office so I usually try something new. If the weather is nice, we may eat on the terrace with the rest of the office. Sometimes we may have a Lunch & Learn where someone will present a topic they are interested in (and it could be anything!).
[13:00] Sometimes I may have more afternoon meetings. This could be anything from reviewing prototypes with the UX Designers, to reviewing bugs that QA testers have raised. Other times it may be pair programming with another dev if one of us needs help.
[14:00] I try to block out my afternoons to spend time working on my individual tasks. This could be developing a component or feature, fixing a bug, or planning the next sprint.
[16:30] Attend the Hub Townhall which happens every 2 weeks. It’s a chance for us to learn about any new developments happening across Hub such as client feedback, new contracts signed, new events coming up and even being introduced to the new Hubsters who have joined us.
[17:30] Begin to finish off my work. After, I will either go home or sometimes the office may go out for a drink or food, if I am free I usually join!
The most challenging (and interesting) part of my job is the rate of change. There is always a new problem to work on - sometimes you may work on a solution which turns out to not be the best solution, and you may have to return back to the whiteboard. However, at Hub we follow the ‘Fail Fast’ approach where we try new things quickly to see what works and what doesn’t work. The great factor about this challenge is that it is
actually encouraged to try new solutions as it allows us to innovate.
Firstly, I really enjoy the culture at Hub. There are so many people to learn from and being placed on the same floor means that you will end up in conversations with someone who is working on something completely different to you. It is a great chance to learn from everyone. For example, working with Business Analysts has developed my product and financial knowledge, sitting on the same floor as the CEO and CTO has helped me gain a wider perspective on what I am working on, speaking to UX designers has allowed me to understand what good design is. All of these interactions have made me a much stronger engineer. There is also a strong culture of trust where you are trusted to try new things, despite your prior experience. For example, I was involved in planning the architecture design of the front-end despite having minimal experience in this, within previous roles. Another example is being trained on running interviews which I was really nervous
about before.
Never stop learning or asking questions. You will never know everything about front-end development, but the more you speak to others, read and try new solutions out whilst coding, the more you will learn. Sometimes you have to break your code to understand it better.
