The software engineering world is a whirlwind of knowledge and constant evolution. When I first started my journey at Apollo I felt invincible with Google Stack Overflow and my youthful confidence. “Who needs a mentor?” I thought naively. But then a series of experiences like a cascade of wake-up calls forced me to rethink my perspective and that’s when I discovered the real-life cheat code: a mentor.
The “Relay Race” Project
One project in particular which was essentially a “relay race” of engineers working sequentially brought this realization to the forefront.
Ready to level up your coding skills and unlock a whole new world of opportunities? 🔥 Get yourself a mentor and watch your career soar! Join Apollo’s community and find your mentor!
Before in I had a crucial conversation with Umang my mentor and the Staff Frontend Engineer for the Growth team at Apollo.
The topic: merging changes to the master branch.
We weighed two options:
Feature Branch vs. Feature Flag: A Crucial Choice
Option A: The Feature Branch
This involved creating a dedicated feature branch merging all approved changes there and then finally merging to the master branch once everything was thoroughly tested.
However the potential downside was a feature branch so massive it could have turned into its own zipped archive!
Option B: The Feature Flag
This approach advocated for continuously merging changes directly into the master branch but keeping them hidden behind a feature flag.
This felt like the more promising option for several reasons:
- Reduced Risk: Feature flags allowed us to release changes incrementally reducing the risk of breaking the production environment.
- Faster Iterations: We could iterate quickly and get feedback from users without waiting for a full release cycle.
- Simplified Deployment: It simplified the deployment process as we were always merging into the master branch.
Umang with his seasoned experience steered us towards the Feature Flag approach.
He highlighted its adaptability and ability to manage complex deployments ensuring a seamless transition to production.
This insight a simple yet potent tip solidified the importance of having a mentor who could guide us through these critical decisions.
Beyond the Frontend: A Nudge Towards Backend Knowledge
But the value of mentorship extended beyond mere technical guidance.
As a senior frontend engineer Umang emphasized the immense benefit of having “a bit of” backend knowledge particularly within my own product area.
This advice resonated deeply.
Following his suggestion I took on a low-risk project that involved backend work.
It wasn’t about becoming a backend expert overnight but about taking those initial baby steps making small but meaningful contributions.
Ready to level up your coding skills and unlock a whole new world of opportunities? 🔥 Get yourself a mentor and watch your career soar! Join Apollo’s community and find your mentor!
Ready to level up your coding skills and unlock a whole new world of opportunities? 🔥 Get yourself a mentor and watch your career soar! Join Apollo’s community and find your mentor!
This experience was a turning point.
It built my confidence reduced my dependency on backend engineers for initial debugging and eased my apprehension about venturing into unfamiliar territory.
It was a significant learning opportunity within my working domain a testament to the power of stepping outside your comfort zone and exploring new avenues.
The Power of Custom ESLint Rules
With Umang’s encouragement I took another leap and ventured into building custom ESLint rules something completely new to my front-end career.
His unwavering support opened up new possibilities and I soon found myself confidently navigating this uncharted territory.
One of the ESLint rules I developed aimed to centralize environment variable usage.
It required all variables to be defined in a single file which streamlined tracking and management making updates easier and significantly enhancing code maintainability.
This rule a small but impactful contribution was born from my own frustrations with the existing setup and the desire to make a positive impact on the codebase.
This experience wasn’t just about learning a new skill; it was about taking ownership identifying a pain point and finding a creative solution.
It was a testament to the power of collaboration where a mentor’s guidance and support fueled my own initiative and drive for improvement.
Expanding Horizons: Accessibility and Design Systems
My journey of growth wasn’t confined to backend or ESLint.
I also had the opportunity to collaborate with the Design System team contributing to core UI components and expanding my expertise in accessibility.
This unexpected collaboration opened doors I never knew existed exposing me to new perspectives and enriching my skillset.
It’s amazing how a mentor’s guidance can lead you down paths you never imagined fostering a spirit of curiosity and continuous learning.
They become your guiding light illuminating areas you may have overlooked and opening up new avenues of growth.
The Mentor-Mentee Dynamic: A Collaborative Journey
It’s important to acknowledge that the mentor-mentee relationship is not a one-way street.
It’s a collaborative journey where both parties learn and grow.
My mentor Umang wasn’t just imparting knowledge; he was actively listening offering feedback and celebrating my wins along the way.
He challenged me to think critically pushed me to step outside my comfort zone and provided the encouragement I needed to persevere through moments of doubt.
Seeking Mentorship: Embracing the Journey
Having a mentor is like having a trusted friend who understands your goals provides guidance and celebrates your achievements.
It’s someone who sees your potential and helps you realize it.
If you’re seeking mentorship remember that it’s not about finding a perfect mentor but about finding someone who resonates with your goals and values.
It’s about finding someone who inspires you challenges you and pushes you to be your best self.
Embrace this journey of self-discovery.
It’s about learning growing and becoming the best version of yourself.
With the right guidance and support you can achieve anything you set your mind to.
And remember “Help shall always be given at Apollo to those who ask for it!”