Gynger Career Growth & Development

How often do you take time to focus on knowledge- and skill-building? 

I stay on top of my engineering skills by consistently building, whether that’s solving real-world problems at work, working on side projects or taking project-based courses. Hands-on experience is far more valuable to me than passive learning. When I want to explore a new concept or technology, I turn to a curated list of trusted engineers in specialized areas. With so many opinions out there, it is important to cut through the noise and focus on reliable sources.

I keep up with new trends but prioritize depth over hype. Rather than chasing every new shiny tool, I focus on technologies that are relevant to my work in web development and fintech. I also pay attention to patterns in tech evolution to anticipate what will have a lasting impact.

When I am passively learning, I enjoy reading books on topics of interest. I have collected a whole shelf of programming books over the years that I have barely scratched the surface of.

It is hard to put an exact number on it, but I would estimate that I spend at least three to four hours a week dedicated to expanding my knowledge and skills.

What are your go-to resources for keeping your engineering skills sharp? 

I follow a select number of news articles and blogs religiously, making sure to read everything they publish. I don’t subscribe to much content, but when I do, I prioritize it. Beyond that, my learning is fairly evenly split between YouTube videos and official documentation. Work projects often introduce new tools or third-party services, so I always start with the formal docs to build a solid foundation. Reviewing pull requests is another great way to sharpen skills. Seeing how coworkers tackle complex problems and asking clarifying questions helps expand my own understanding.

What does the learning culture look like at your company or on your engineering team? 

The learning culture on my team is strong. Everyone clearly wants to share their insights and continuously improve. Pull requests are the best places to spark discussions and help everyone level up. Everyone is encouraged to ask questions, challenge assumptions and explore better ways to solve problems. It’s a culture that values learning in the flow of work rather than treating it as a separate activity.